Good day all, first timer posting but have been reading the forms for a while now.
I have a major problem with my galaxy note GT- N7000. I have browed through the forms and have not seen a problem like mine. I really need help with my phone.
Problem:
The phone is rooted with paranoid android rom; current version PA_n7000-3.60. I have been using this for over a year with no problem, when all of a sudden the phone goes into android update screen and ever since been on that screen whatever I do. I never tried to update the rom or anything when this happened, just found it like that. All auto update are turned off.
I have tired installing the rom again using CWM and even tried installing the latest update still the problem persists.
I don’t want to format the phone because I have some very important information I will lose if I do. Cannot back up using CWM, getting error messages, cannot get access to phone via connection to my computer. I am in a jam and really need help with this.
Thanks.
Related
Hello everybody.
I am having serious trouble with my phone and I was hoping some of you might be able to help me out.
I just bought my SGS 3 days ago. It came with android 2.1.1 eclair installed.
I had read that that version was not the best ( the first thing I saw when I opened the phone actually was an error screen, and the lag was horrible) so when I got home I decided to try and upgrade it using the official software for it (Kies).
Unfortunately Kies would simply disconnect my phone when I told it to upgrade, after which it would ask me to upgrade again >.>
So I decided to use Odin to flash one of the newer 2.2.1 versions.
I flashed a 'JS3' version with a repartition to 803 pit , but it crashed after rebooting with the dbdata error (which as I learned later was caused by not flashing a full firmware).
I flashed JPU after which worked great. It was fast and responsive.
However my phone kept crashing. Whether on standby, using apps, or just trying to dial a number, it would freeze, start vibrating, and sometime reset, other times just stay frozen until I force shut down it from the power button.
I flashed JS5 afterwards, with full cache clearing, factory reset etc. Still crashed.
Then I tried flashing Darky's 9.2 Ressurection. Loved it but I couldn't even set up my google account because it crashed constantly.
Then I went back to what I believe is the current official version for my location and carrier (Vodafone Romania), JP9 .
After flashing it didn't crash, but after a while (one night), it started crashing like crazy, even wound up with weird gray lines and a freeze in the morning.
I was hoping someone here might know what is wrong with it. I already sent it back to be serviced but I am thinking maybe I broke it somehow and would like to know how so I don't do it again.
The phone is network locked, which I later learned is usually a bad thing for flashing, unfortunately I didn't know about that when I started.
well first of you want to remove the network lock so try these:
http://forum.xda-developers.com/showthread.php?t=761045
http://forum.xda-developers.com/showthread.php?t=913681
next step is to register on www.samfirmware.com (its free) and here is where you will get all the latest official firmwares from samsung..
what you want to do is download (XWJS5) with all 3 files and PIT and flash that through odin with RE-PARTITION..
Before you do that, put your phone into recovery mode (volume up + Home button + Power button ) and do a factory reset / wipe cache ect...
so when you have done that and flashed the new firmware. let me know what the outcome is..
another thing.. ALWAYS MAKE SURE KIES IS CLOSED.... EVEN IN THE ICON TRAY... AND MAKE SURE DRIVERS ARE UP TO DATE.
other than that you shouldn't have any problems
hi, thanks for the advice.
I already did most of that however. I did a factory reset numerous times, and I also did a full repartition flash more than once, to no avail.
I am waiting to get it back from warranty service now but I am wondering what went wrong.
Was it broken when I bought it or did I damage it somehow by trying to flash it while network locked ?
flashing with network lock wouldnt make everything force close. the worst thing that could happen when flashing with network lock is not picking up a signal and possible IMEI corruption.
i think you may have just flashed the wrong ROM, it happens to us all, but the more you do it the more experienced you become and you soon learn methods to restore things..
dont worry too much it will be fine when it comes back from samsung, just be sure to read up properly if you have any doubts.. or ask a question first you will get a reply quicker than you can Unbrick your phone..
My phone seems to hate the 803 pit file. Lots of force closes when I used it. Try using 512, see if that works any better.
Hey everyone, this is my first time posting on a forum, everytime ive had a problem ive been able to find the answer to it. However today seems to be the day ive hit a brick wall. Upgraded a couple of weeks ago to ICS 4.0.4 on my uk galaxy note, and like many other users experienced a few bugs. I took it upon myself to downgrade back to gingerbread. I backed up my galaxy note using Kies before the downgrade. The downgrade went okay, had to wipe all data due to issues but i thought this wouldnt be a problem due to the back up i made. However i have now found that i cannot restore for whatever reason (suspect its because of the different firmware).
I tried to extract the SBU file using SSV card extractor to atleast get my contacts work but i had no luck working it.
Please if anyone can help me? Would upgrading back to ICS 4.0.4 allow me to recover files?
Thanks for your time.
Hi guys and gals.
I've been flashing roms for years and I've soft bricked my devices dozens of times and have always been able to recover, except this time.
I was running Cyanogen mod 12.1 and all the problems started happening after a nightly update. Basically, the phone got super laggy and eventually started random rebooting. I thought it was a bad flash or something was wrong with the latest update so I did a clean wipe and flashed another rom, same thing happened. Eventually I Odined back to stock and it ran fine for a few days but the problems came back. Now the phone won't even finish boot anymore. I used NAND erase all in odin and and reflashed again, it seems to be better since it wont reboot its self anymore but I can't get past the T-mobile splash screen. Last night I tried reformating the NAND using a PIT file but I kept getting "Secure check fail : PIT". I was starting to thing the problem is hardware related but it won't RR in download mode and I think its too big of a coincidence that it happened after the Cyanogen update. Any ideas?
My first and always main advice is that if you are unsure about your hardware the first step is to Odin back to stock. The reason is because it is a bit for bit rewrite back to the way the phone was intended to be run as long as you do a factory reset from Stock Android Recovery before it boots. This is how your phone was when it came out of the box and it is a great way to check if it has a hardware issue by looking for bad behavior when using the original drivers.
If you flash back to stock completely clean and your phone is still acting crazy you might have bad blocks on your NAND, you might have issues with your RAM/CPU, or it might just be a loose hardware connection from heat or impact. But you can only truly diagnose those from Touchwiz because the drivers are first-party, not reverse engineered to be compatible. If you can reinstall all your apps and use it normally for a week then your hardware is good and CM was the problem and you should try another AOSP build.
I am on the 09/09 Nightly for CM and I can tell you that I have no lag or issues on my device at the moment for what that is worth. Good luck!
Thanks. I might just send it into samsung and see what happens.
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I'm sure there are several possibilities that could be software related. However, I've had this issue on a couple of my older phones and it just turned out that the power button was sticking. Just had to pull the phone apart and clean it.
If nothing else seems to work for you, it wouldn't hurt to check this.
PS: I have 4 boys who like to play on the devices with sticky fingers.
The story
Hi everyone, thanks for reading me and thanks for your time.
I am stuck with this galaxy S5.
I got a S5 in the past, a beautiful SM-G900F on which I run lineageOS no problem whatsoever.
I bought another S5 from ebay, turns on it's a G900A.
Had problems from the start, the phone seemed to often restart instead of turning off normally, and I had severe battery drain both while on and while turned off. So I went to this section and looked at Root, Roms and other cool stuff and followed the guide to put up a custom ROM.
The problem
The first step, installing the experimental firmware, seemed to work but after reboot no OS would install, instead I got "MODEM CRASH".
So from there, I tried to roll back to stock.
I put on BOF3, which works, but since then I have baseband null and IMEI unknown.
Panicking, I tried to install COI5, but same problem there and also multiple bugs, so I went back to BOF3 and it's all functional, but same baseband/IMEI problem.
I have tried to reset to the oldest stock G900AUCU1ANCE but ODIN fails at the very start. I seem to understand I'm on android 5 and cannot rollback now, somehow.
If anyone has any idea on what I can do realistically.
I have no EFS backup as when I started I didn't know what EFS was.
Thank you all for your help.
I have seen many topics with this problem but I have only been confused more by them so forgive me for posting here.
Bump!
Can anyone help?