OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
arvichan said:
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
Click to expand...
Click to collapse
Be in safe kernel if your on ics. You could check your device of the bug by downloading eMMC check in google play. Dont put your fate in that if your on stock ics rom not rooted you will not get the bug, be on the safe side.
arvichan said:
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
Click to expand...
Click to collapse
Just check the service job sheet whether they replaced the mobo or not before taking the delivery ? As simple As that.
got my gnote back with new mobo
Well, it is almost like the 'law of attraction'... I didn't want any problem and when I got my gnote today... guess what ? phone vibration didn't work. I had to go back to the SSC.
Fortunately, they responded immediately and the SSC guy fixed it on the spot without another round of formal servicing process. As explained to me, an insulation sticker of the vibrator was not removed while slipping in the new mobo. I didn't care less to understand if that is true as I was excited to get my phone with 11GB internal storage .
All seem to be working fine as of now with stock ICS 4.0.4 :good:
Related
Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?
What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.
Just use odin 1.3 reflash official rom , everything would be OK.
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?
You mean the external sdcard? Maybe try to format it...
OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...
Hi Guys...
I got a Galaxy Note GT-N7000, and its been more than a week i tried to revived it using the any method i've found in this great forum.
So let me tell u guys the stories of my Note :
1. It was always updated OTA so the last ROM i used is Indonesian Note ICS 4.0.4
2. One day (last Friday) while i was browsing Internet using it, it suddenly got very hot, and the battery seems like draining very fast
3. In the mid day it reboot by its self, and entering countless reboot... a never ending reboot
4. So i tried to enter recovery, and yes sadly i've might triggered the emmc bugs by doing factory reset. But i'm not sure i've done it or not, coz i've a CWM recovery installed.
5. Anyway then i tried to flash stock room found in dr.ketan's thread...many thanks to him for those collection using PC ODIN and i got the "factoryfs" stuck problem
6. I also tried to flash countless kernel over and over, tried install Stock GB and ICS, tried RocketROM, CM10 and it all failed. In dowload mode i still got a Stock Firmware installed. So any ROM i've tried to install using Kernel didn't succed.
7. So i decided to take it to Samsung Service Center nearby, and i found that my battery is BAD, it wont charge (wonder would it because of the battery i got that problem in the first place). Since i got this Note for around 8 months, and the warranty for the battery is 6, the make me bought the new one, ordered and available in 2 days.
8. So I get back to the service center, put the new battery restarted the phone, and it stop on samsung logo (no yellow triangle there). So I complained, and they look into it, and said we may try to install new software, but there's a risk that your Note got damaged. They said the risk is mine and they wont have any responsible for it.
9. So furiously i bargain about my Warranty (12 month), coz the said that i've updated the ROM my self, so i explained to them that it was OTA's update, all i do was press YES, and they said even OTA official update will cancel my warranty. Its getting weird, i got angrier and they just said its their company procedure so there's nothing they can do to help me. So Samsung Indonesia will cancel warranty for every attempt to update the ROM OTA's, only their service center is allowed to do so. Wasted my valuable working hours there...
10. So i get back, determined i officially will do anything to get this Note life back. So i started to look at Forrest1971 (many thanks to him) thread about bricked note and tried many kernel and got one working with adb (T-Kernel V0.9) doing the checking and found faulty partition 9 and 10 and doing the step and finally got the partition fixed. Lost 3GB of space.
Then here came the real problem :
1. Still wont work with ODIN, stuck at Factoryfs with stock ROM GB N7000DXLC2_N7000OLBLC2_N7000DXLC1_HOME.tar and ICS N7000DXLR5_N7000OLBLR2_N7000DXLR1_HOME.tar. But working fine flashing Kernel so my guess it is not the connection problem. I've tried on 1 PC, 2 Laptops, 2 OS (Win7 32bit and WinXP 32 bit) still the same.
2. Then i tried to flashing via Kernel (CWM, Abyss, T-Kernel, CM9 Safe Kernel) i got to do trial and error coz not all ROM can be installed using any given Kernel. Seems that T-Kernel v0.9 is working for most of the ROM. Sorry i didn't keep note about the kernel-rom coupling. Here is the list of ROM i've tried :
cm-9.1.0-n7000 + gapps-ics-20120429-signed
cm-10-20121209-NIGHTLY-n7000 + gapps-ics-20120429-signed
RocketROM v2 XXLS7_stock_odexed
SuperNexus-N7000-BUILD5-20121017 + gapps-jb-20121011-signed
RocketROM_ICS_XXLPY_v1
3. All of those ROM came out with the same problem :
- Freezing on the Samsung/Mod Logo Screen (Got very HOT)
- Entering the "Andoid is Upgrading" and then updating Apps but stuck at random number (# of ###) (Got very HOT), i've tried to wait overnight but stay on the same number
- Succeeded boot up but Freeze after couple of minute (Got very HOT)
4.All those problem seems happened randomly, but most of the time it happened like this :
Stuck and Logo Screen - Reboot by me - Stuck and Upgrading - Reboot by me - Boot fine, but freeze very soon - Reboot by me, and back to the Logo stuck... (but still sometime its just random), the only thing same that it got very hot.
5. This is my last resort, i'll try to flash Supernexus, CM9 or CM10 without the GApps. Now i'm on Supernexus ROM, not yet freeze while i'm typing this. But without the GApps i wont have G-Play, and cant reinstall Apps that i bought in G-Play. Dilemma...
So any thoughts or advices will be greatly appreciated...
I really like this phone, wish i can revived this phone... :fingers-crossed:
Thanks B4 for any comment...
Well, i guess no one have the same problem here...
I'm running the rocket ROM ICS right now, this is the one ROM that got me closer to "STABLE" state.
Still got self reboot, most of the time when i'm using browser (Android, FF, Chrome), or after a long run on youtube or downloading something.
I've also tried the PA Experia ROM by AmniX : http://forum.xda-developers.com/showthread.php?t=2100083
But it was worse than rocket ROM ICS, more likely have the same symptom with the CM9/10 i've tried.
So seems like i've to manage to use this defect/handicapped gadget... :fingers-crossed:
diasdroid said:
Well, i guess no one have the same problem here...
I'm running the rocket ROM ICS right now, this is the one ROM that got me closer to "STABLE" state.
Still got self reboot, most of the time when i'm using browser (Android, FF, Chrome), or after a long run on youtube or downloading something.
I've also tried the PA Experia ROM by AmniX : http://forum.xda-developers.com/showthread.php?t=2100083
But it was worse than rocket ROM ICS, more likely have the same symptom with the CM9/10 i've tried.
So seems like i've to manage to use this defect/handicapped gadget... :fingers-crossed:
Click to expand...
Click to collapse
I would complain to the service center. It's absolutely rubbish that an ota update voids warranty, they're lying through their teeth and I wouldn't stand for it. So long as you have no trace of custom rom or root, they are required by law to fix the phone or replace it within 12 month warranty. If you'd left traces of root or Cwm that's a different story.
Try a second repartition, often a first scan will not find all bad sectors, run through it again just to be safe. Also, after repartitioning its usually the case that stock or tw based Roms won't work without freezes and reboots because they occupy too much space on the emmc. You're best with cm or aokp Roms.
Sent from my GT-N7000 using xda premium
Today, my Note got extremely bricked, that I could not believe a phone like that could get so easily blown up.
I get this "Firmware update encountered an issue. Please select recovery in Kies and try again." message while it's rebooting every second.
I got this by making a huge mistake, using the re-partition option with the included .pit file, thinking it would factory-wipe the phone before downgrading... well, it didn't. Now, I can't barely access Download Mode or recovery because of, what I assume, low battery. It's charging now and it doesn't look like it. It reboots itself every 5 sec while it's plugged in. Before that, I used the JB leak and began to hate it because of it's damn instability. I wanted the stable, stock, ICS that came with it. I never had any problems like that on Xperia S.
Hell, even Odin can't ****ing save it because of the reboot-problem. I begin to think that, for the first time ever, I have to send this pile of **** back to Samsung and get a new one by saying, Kies ****ed up my phone.
Is there a solution that DOES NOT INVOLVE A DAMN USB JIG for this phone?
If you got the error in kies you could have followed the kies emergency firmware recovery option. Reflashing with a pit file is only for when you have triggered the emmc brick bug is my understanding. Look for the thread with the unbricking guides and hope for best. If not then it looks like service centre...........
Sent from my GT-N7000 using xda app-developers app
LinixAndroid said:
.. I could not believe a phone like that could get so easily blown up.
I got this by making a huge mistake, using the re-partition option with the included .pit file...
Click to expand...
Click to collapse
Did you really read and combine this two sentences? Sometimes people should read the warnings (here about the reasons why NOT to use a pit) and follow them.
But first of all you should recharge the battery outside your device. When you're sure it's "reloaded" try download mode again and install a prerooted Stock Rom (like GB LC1 3-part) and check if you can install and after reboot into a stable device again.
Maybe it isn't so bad forever only for a few hours.
ThaiDai said:
Did you really read and combine this two sentences? Sometimes people should read the warnings (here about the reasons why NOT to use a pit) and follow them.
But first of all you should recharge the battery outside your device. When you're sure it's "reloaded" try download mode again and install a prerooted Stock Rom (like GB LC1 3-part) and check if you can install and after reboot into a stable device again.
Maybe it isn't so bad forever only for a few hours.
Click to expand...
Click to collapse
Wait, I have to charge it outside the phone? What kind of charger only charges the battery outside the phone?
just find someone with the same phone in your neighbourhood and charge in another phone...that's the easiest way..
I have flashed my note multiple times now and it never crossed my mind to use a .Pit file..
By the way, have you thought of leaving the battery out for a few minutes? I got that Firmware issue message before because the power went out while I was flashing my phone from my PC.. Then I just left it out for a few minutes and was able to boot back into dowload mode again
After the emmc brickbug:
The custom pit file may work but trust me after a few moths you going crazy with your phone... it freezes randomly on every rom and wont charge randomly. When you wake up.. phone frozen and battery is on 0% ... i lived 2 weeks with this then i gave it to samsung and they changed the mainboard for free now im happy
ok so i was running a devil kernel on jellybean 4.2 and for some strange reason the rom started acting funny and gave me a message saying i had to type in a password ti decrpyt storage even though i have no passwords on my samsung I897. So i decided to flash back to stock and start all over again from scratch using odin one click but in the middle of downloading my phone was disconnected and it gave me the bricked screen shortly after. Now i am unable to do anything on this phone ive tried pushing the volume buttons and taking the battery and sim card out while running odin 3 again trying to force it back into download but so far no progress has been made. If any one can help me it is much apprecitated.
theklxn said:
ok so i was running a devil kernel on jellybean 4.2 and for some strange reason the rom started acting funny and gave me a message saying i had to type in a password ti decrpyt storage even though i have no passwords on my samsung I897. So i decided to flash back to stock and start all over again from scratch using odin one click but in the middle of downloading my phone was disconnected and it gave me the bricked screen shortly after. Now i am unable to do anything on this phone ive tried pushing the volume buttons and taking the battery and sim card out while running odin 3 again trying to force it back into download but so far no progress has been made. If any one can help me it is much apprecitated.
Click to expand...
Click to collapse
Which Odin did you use? When already on JB, you should be using Odin KK4 without bootloaders to avoid hard bricks.
If your Odin was flashing bootloaders when it got interrupted, chances are that it's hard bricked and only JTAG service will bring it back. You can contact Josh at mobiletechvideos.com for it (of course there's a fee for the service).
You can try a jig before going through JTAG service (build or buy one), maybe you'll get lucky and be able to force download mode but know that if it got interrupted while flashing the BLs, only JTAG can bring it back.
i was afriad you might say that didnt think i would have to go that far to bring it back but thank you for the swifty reponse ill get back to you when my problem has updated
Hello.
I have a Galaxy Note 4 SM-N910T2. In january of this year i upgraded it to 6.0.1 (N910TUVU2EQI2) from 4.4.4(N910T2UVU2AOG1) using the SM-N910T firmware for the upgrade, everything was working perfectly but the day before yesterday i wanted to perform a wipe cache because the phone was being a bit laggy. after the wipe cache was perform and i hit the reboot, the recovery got stucked on Verifying DMhash tree. so after 30 minutes i took the battery out and powered on my phone, the problem is: The phone started to freeze, reset it self even the process system crashed. I read that downloading the Wake Lock power management helps and it did but i didn't want to use this app forever so i downgraded back to 4.4.4 it's original firmware, it does run better but now my phone reboots itself and it freezes just a little bit. Also i've got the Process system is not responding do you want to close it?
Things i've done so far:
1- Reflashed 4.4.4, 3 times, i've done wipes before reflashing and after. Nothing
2-Flashed TWRP wiped everything, repaired the file system, Flashed the stock again (4.4.4) nothing.
I'm not going back to 6.0.1.
Do i have to buy a new phone or maybe a new rom with a kernel will help ?
Pigoath said:
Hello.
I have a Galaxy Note 4 SM-N910T2. In january of this year i upgraded it to 6.0.1 (N910TUVU2EQI2) from 4.4.4(N910T2UVU2AOG1) using the SM-N910T firmware for the upgrade, everything was working perfectly but the day before yesterday i wanted to perform a wipe cache because the phone was being a bit laggy. after the wipe cache was perform and i hit the reboot, the recovery got stucked on Verifying DMhash tree. so after 30 minutes i took the battery out and powered on my phone, the problem is: The phone started to freeze, reset it self even the process system crashed. I read that downloading the Wake Lock power management helps and it did but i didn't want to use this app forever so i downgraded back to 4.4.4 it's original firmware, it does run better but now my phone reboots itself and it freezes just a little bit. Also i've got the Process system is not responding do you want to close it?
Things i've done so far:
1- Reflashed 4.4.4, 3 times, i've done wipes before reflashing and after. Nothing
2-Flashed TWRP wiped everything, repaired the file system, Flashed the stock again (4.4.4) nothing.
I'm not going back to 6.0.1.
Do i have to buy a new phone or maybe a new rom with a kernel will help ?
Click to expand...
Click to collapse
All i can say is your phone mmc chip is about to die soon or later you will get mmc_read failure message and your phone wont be able to boot into the system and you won'tbe able to flash anything.
My best suggestion is sell it ASAP.
Trex888 said:
All i can say is your phone mmc chip is about to die soon or later you will get mmc_read failure message and your phone wont be able to boot into the system and you won'tbe able to flash anything.
My best suggestion is sell it ASAP.
Click to expand...
Click to collapse
I came across the mmc_read failure before I realized it was happening and have been researching ways to at least verify there was nothing important on the device before retiring it to Samsung heaven.
Instead of useful advice, everyone seems to be spouting "sell it ASAP" as though it doesn't make you trash as a person to attempt selling it as any sort of working device. The inclusion of "ASAP" and lack of "with a disclaimer" tends to suggest they aren't recommending you actually tell anyone about the issue.
Good advice would be to back up everything you can now and begin looking for a new device. You could attempt to sell it for parts, but make sure to inform people of the situation. If it is that close to failure, chances are it will still be well within the 30 day return policy on most sites and they always favor the buyer. Your device is already ruined, but there is no reason to destroy your reputation with it.