Cant install new rom. Fail at factoryfs - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hi !
I was trying install Criskelo Rom v8 fom RocketRom v7. Phone catch bootloop so i tried to install via odin. Then fail on factoryfs i was trying on 3 computers win 7/xp and other ports. Every time fail on factoryfs. I decided to give back my note to serwis. I have reset binary calculator and yellow triangle and i have installed stock kernel. When i'm turning on my note it shows recovery there is an image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can i recieve my note to serwis like that ? or need to do something else ... Thanks for help !

It seems from the photo that you arent on custom kernel.
If your binary count is zero, take it to the service center and tell them that after update, the phone booted and didnt start.
Do not tell them about custom rom that you flashed, else it will not be covered under warranty.

apurvapatel said:
It seems from the photo that you arent on custom kernel.
Click to expand...
Click to collapse
I need to install custom kernel via odin? I did it with "stock_kernel_N7000XXLC1" is it correct ? if not please for link with correct kernel.

mihassone said:
I need to install custom kernel via odin? I did it with "stock_kernel_N7000XXLC1" is it correct ? if not please for link with correct kernel.
Click to expand...
Click to collapse
Yes stock kernel is correct. Thats the European kernel, right?
Now confirm via download mode (vol down + home + power) if your binary count is zero at the moment and via recovery mode if you have the Yellow Triangle. If its zero and there is no yellow triangle, your phone is good to go to the service center. Do not flash any other kernel or rom now over the stock one.

Is this problem called super brick?? Having the same problem now. If possible, I want to fix it without jit or sending it to a service center.
Sent from my GT-N7000 using xda app-developers app

There is soft brick and hard brick. Generally speaking, from what i understand, soft brick can be repaired. It is a software problem. Hard brick is hardware gone wrong.
I have been through the factoryfs write fail twice. Got it repaired under warranty both the times.
Basically, because of this bug in the stock ics kernel from samsung, any time a factory reset or wipe is performed, it corrupts the physical memory. It creates bad sectors and when anything tries to read or write on that part of the memory, the task freezes. Hence odin stops at factoryfs.
There is a work around to this. Repartition the memory and skip the bad blocks. Basically by trial and error you shorten certain partition as per the physical damage on the chip. Sometimes it works, but you loose about 3gb of your 11gb internal usable memory.
There is a guide by Forest hereon xda. It is time consuming. And it is a work around. Not a solution. Plus, you memory remains corrupted.
I have tried the repartition thing both the times. Once a rom worked, the phone coughed up more bad blocks. It went on until i got fed up and sold off the phone.
I would advice that if the phone is under warranty, get it repaired. Back from the rrepair, first thng, check if its got its full 11gb memory intact.
Apurva

People are still getting bricks with all the warnings? Samsung fix this!
Sent from my GT-N7000 using Tapatalk 2

Samsung doesnt post a statutory warning on its boxes! Who would think a brand this reputed would have such a fatal flaw! One seaeches only after geting affected by the bug... how will people not trust stock recovery?!

Related

Galaxy S stuck with orange triangle

Hi guys,
I 've seccesfully used JM7+Voodoo lagfix and I decided to flash the jm7 again because of the bug in Voodoo beta 3 which keeps the processor 100% all time long.
According to the instructions on voodoo lagfix website, you have to convert the filesystem from ext4 to RFS again, I did it succesfully.
Then I used odin, put the phone in download mode, usb cable and START on odin.
Problem is that odin was:
when I pushed start I got an error , and it didn't start, removed cable.Start again in download mode, start odin, then start again...
It did start but it was stuck on "do not turn off target!!!" for few minutes. So I had to stop it ( odin was running locally but my csc modem and code files were on a samba share, never took so long before )
Now when I turn on the phone I get an image like:
a pc and a mobile phone with an orange triangle with an exclamation point into it
and it won't start.
I have just the samsung usb drivers installed, and before doing this I did remove kies to save some space on C:
This is the first time it is behaving like this.
Did I brick the phone?
Thanks in advance any help is really appreciated.
P.s. at the moment I am installing kies again, download updates, and I ll try odin again.
you mean like this http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/GT-I9000
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and now this?
all you need to do is go back to the download mode, which is this
then you can flash with Odin again
make sure all files are local
I mean the second image you posted mate.
Now it looks better guys!
I have reinstalled kies and used odin succesfully again.
Thanks again.
gettons said:
I mean the second image you posted mate.
Now it looks better guys!
I have reinstalled kies and used odin succesfully again.
Thanks again.
Click to expand...
Click to collapse
How were you able to get back to download mode? I did the same as you (unplugged when a flashing froze up) and can't get back to download mode..
Just that terrible 'orange triangle with exclamation mark' connect to PC symbol (does anyone know the technical name for this screen?)
Geo_Droid said:
How were you able to get back to download mode? I did the same as you (unplugged when a flashing froze up) and can't get back to download mode..
Just that terrible 'orange triangle with exclamation mark' connect to PC symbol (does anyone know the technical name for this screen?)
Click to expand...
Click to collapse
It's called "Black screen of death"
Sent from my GT-I9000 using XDA App

[Q] Help - Boot endless loop - :( Please help

Hello,
After installing the OCLF my phone is now in an endless boot.
I am unable to go into recovery mode, but download mode still works.
I have tried reflashing my device with "re-partition" and "efs clear" on,
Unfortunately I am still getting the endless boot
I have a galaxy-s i9000M with the current i9000 jpk rom.
I have used this rom for a long time, so I am confident that the OCLF had an error and semi-bricked the device
Does anyone have a solution??
Thanks
Recover jpk firmware in your phone.
I have tried that, every time I recover any firmware it still is the endless loop.
Although one time I managed to get into the recovery, and there was an error message saying "unable to mount sd"
Here is a picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry but you're gonna have to flash your firmware again.
AdamDowning said:
Sorry but you're gonna have to flash your firmware again.
Click to expand...
Click to collapse
I have, still goes to the recovery
Should I recover the modem and csc of my original firmware as well?
i am having the exact same problem. i noticed that using the UGJH2 PDA can stop the endless booting, meaning that it actually takes you to the "S" logo. However, after the "S" logo the screen goes completely black, but you can still see the Back and Menu buttons lighting up.
Request: DOES ANYONE HAVE THE CSC AND MODEM FILES TO UGJH2. Please its a matter of life and death.
Sorry to be the bearer of bad news. But your internal SD card has failed. Your only option at this point is to send the phone in for repairs. I do suggest flashing back to stock UGJH2 prior to doing so though.
arianR10 said:
i am having the exact same problem. i noticed that using the UGJH2 PDA can stop the endless booting, meaning that it actually takes you to the "S" logo. However, after the "S" logo the screen goes completely black, but you can still see the Back and Menu buttons lighting up.
Request: DOES ANYONE HAVE THE CSC AND MODEM FILES TO UGJH2. Please its a matter of life and death.
Click to expand...
Click to collapse
Same issue here, what carrier are you with?
Electroz said:
Sorry to be the bearer of bad news. But your internal SD card has failed. Your only option at this point is to send the phone in for repairs. I do suggest flashing back to stock UGJH2 prior to doing so though.
Click to expand...
Click to collapse
I figured that is what was wrong,
Heading to the store right now, hopefully they can just swap them
arianR10 said:
i am having the exact same problem. i noticed that using the UGJH2 PDA can stop the endless booting, meaning that it actually takes you to the "S" logo. However, after the "S" logo the screen goes completely black, but you can still see the Back and Menu buttons lighting up.
Request: DOES ANYONE HAVE THE CSC AND MODEM FILES TO UGJH2. Please its a matter of life and death.
Click to expand...
Click to collapse
The UGJH2 PDA had the modem and csc built into it. You also have a failed internal SD card. Bell/Samsung repair/replacement is your only option at this point.
thanks will do so.
Message to OP: What was the problem?

[Q] I9000 unable to boot.

My sons UK i9000 has a problem, the touch keys were not working and the screen was cracked., so a replacement part was bought and new screen fitted.
The phone booted fine, but the new touch keys did not work, so we tried to update the touch key firmware with *#*#2663#*#* but then the phone refused to boot.
We tried to reflash to a stock rom, which went all ok with odin, but the phone never got past the galaxy s screen.
We have tried loads of different stock and custom roms, including darky's ressurection, but they all either boot to the galaxy s screen and go no further, or boot to the galaxy s screen then reboot after a short while.
Is there anything we can do, we can still access recovery and download mode.
Many thanks.
did you flash the official rom using the ".pit" file? i can only suggest this and this
hope it helps
gigeaky said:
did you flash the official rom using the ".pit" file? i can only suggest this and this
hope it helps
Click to expand...
Click to collapse
Many thanks for the links, tried the gingerbread rom you linked to, phone boots to galaxy s screen, stays there for a while, then constant reboots again.
I'm having the same problem as OP.
Does anybody have any other ideas?
Flash stock JVT firmware (check repartition) use 512 pit, flash Semaphore kernel. Go into CWM recovery, do a factory wipe. It should be good.
Nope, same problem, everything passes ok in odin, but the phone still reboot loops.
Would a faulty touch key cable cause it to do this or maybe something more serious?
Many thanks.
put your device in download mode and use this:
http://files.teamkomin.com/i9000SGS/i9000-XXJVT-One-Click.jar
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to recover my galaxy s I9000 using odin, i had the 512 pit file and stock rom image 2.2froyo, and now mine doesnt even come on anymore, i could get it to go into download mode when the flash failed by taking the battery out unplugging usb, then plug usb in, hold both volume buttons and insert the battery, that worked for me until odin had succeeded, everything was correct, I did days and days of research about it before I went through with it, but now that it successfully flashed, the phone no longer enters download mode or see's any ounce of life, would the jig still work to force the phone to come on?
Tried the one click, first attempt it boots to the first GT I9000 and stays there.
Then tried with flash bootloaders ticked, but bootloops again.
Starting to loose faith in this phone.
if your son's phone was previously on Froyo, you may need to tick "flash bootloaders" in OneClick...

[Q] SGS Not able to boot after re-partitioned..

After flashing MIUI Jelly Beans I wanted to go back to stock 2.3 ROM to check on something and did a restore with CWM which didn't work because (as I've learned later) it uses different file system, anyway I've flashed s1_odin_20100512.pit file alone with Odin, and the result is that I can only turn the phone on in download mode.. What can I do now?
Thanks to everybody in advance..
I've tried to flash stock ROM using the method mentioned in this thread:
http://forum.xda-developers.com/showthread.php?t=1494493
and after finishing, Odin gave me "Fail".. What does it mean and what should I do now?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried to flash it again, now I'm stuck on "Set Partition" on Odin. is it safe to turn the phone off at this point and try again?
Anyone?
ramy670 said:
Tried to flash it again, now I'm stuck on "Set Partition" on Odin. is it safe to turn the phone off at this point and try again?
Click to expand...
Click to collapse
you have KIES running in the background shut it down, get solutions from My Android Solutions for Odin stuck
But First powerdown, pull out Battery, SIM CARD, and EXT SD card, press power
button for a minute , than powerup without SIM and Ext.SD Card...make sure you
have more than 50% battery charge before you attempt any sort of flashing
Thanks a lot, and yes Samsung Kies was running in the background while I was trying to flash, I'll make sure it is shutdown this time, anyway the battery is almost at zero now and the phone isn't charging, so I'l have to wait for a friend who has SGS until tomorrow so I can charge the battery and try to flash the phone again.
On the other hand, I remembered something that might be important, which is that my phone have problems with internal memory (when you have error messages like "E:format_volume: rfs format failed on /dev/block/mmcblk0p2"), not sure if it had something to do with failing to flash stock ROM besides having Samsung Kies running in background (because I got stuck on "Set Partition" in Odin only one time), so there might be something else ausing these problems..anyway I'll try to flash it again tomorrow and see what happens.
Thanks again.
ramy670 said:
so there might be something else ausing these problems..anyway I'll try to flash it again tomorrow and see what happens.
Click to expand...
Click to collapse
Look at My Android solutions again, for other problems, when you Flash bootloader, tick update bootloader too
when you Flash bootloader, tick update bootloader too
Click to expand...
Click to collapse
You mean during flashing the ROM right? or should I flash bootloader separately?
(I didn't touch my phone yet, still waiting for my friend for recharging)
ramy670 said:
You mean during flashing the ROM right? or should I flash bootloader separately?
(I didn't touch my phone yet, still waiting for my friend for recharging)
Click to expand...
Click to collapse
yup, just tick it, can be done separately too
Thanx a lot, the phone is working again, it turned out that you must use Windows account that have administrator privileges in order for the flashing process to work (not sure though cuase I've tried admin account after restart, so may be restarting PC was the answer)

Help! Getting TWRP on this damn phone...

HELP!
S20 FE 5G SM-G781B.
I am at my wits end here. I have tried and tried, but, nothing... tried flashing TWRP with Odin multiple times (and versions), get a A-OK, installed fine, then try to boot into recovery... and it's just standard recovery.
You must disable auto reboot in Options tab in odin.
I've done that. No Bueno. I've been (trying to) follow this guide, but when it comes to the "press Vol Up+Vol Down+Power Button to enter Recovery" it just... doesn't work.
EDIT: Well, with USB connected Vol Up+Vol Down+Power Button just dumps me in Download Mode...
Try volume up+power only.
That just boots me into the standard recovery.
Thanks for taking time to help me, btw
Try another version of odin then
I SWORE I had tried different versions of Odin.. I have 3 versions downloaded (3.10, 3.12, 3.14). Odin3 v3.12 did the trick... somehow... so far, so good. But of course, when one problem seemingly gets solved, another one arises...
I can't find the zips (multidisabler-samsung-2.6a, Magisk-v21.4) in TWRP. I'm about to chuck this stupid phone out the window.
EDIT: I hate this stupid phone. One step forward, two steps back...
does usb connect to computer?
Yes. But when I connect in TWRP I just get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And I can't copy any files to the Internal Storage.
Connecting 'normally' I can access my SD card and Internal Storage as normal.
It seems like the TWRP fried something on your phone......Does 'adb push files' work(I can elaborate on this if needed)
Figures Hope it's nothing irreversible.
The TWRP I'm flashing is twrp-3.5.0_10-2_afaneh92-Q-r8q. You know if this is the right one?
What android version are you on?
11
Then you have used wrong TWRP, as expected. This is the right one:
twrp-3.5.0_10-2_afaneh92-r8q.tar | by mohammad.afaneh for Galaxy S20 FE 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Friendly Remind you that you need to reboot directly into download mode and flash this recovery(i.e.AVOID booting into stock rom)(Surely, disable auto reboot)
Q means built for Android 10 and R means built for Android 11.You used 10 TWRP on 11 ROM so it is buggy.
Good to know about the Q/R difference, thx.
But flashing the R version yields the same results
herringson said:
Good to know about the Q/R difference, thx.
But flashing the R version yields the same results
Click to expand...
Click to collapse
Nooooo! That may really be a irreversible damage. Try factory reset in TWRP or/and reboot into stock rom, which may help.
herringson said:
I'm about to chuck this stupid phone out the window.
Click to expand...
Click to collapse
I am afraid if this nightmare come true
herringson said:
Figures Hope it's nothing irreversible.
Click to expand...
Click to collapse
Maybe more than figures. The whole data partition can be corrupt. Factory reset (format data) in TWRP for android 11. Hate to say but you have to say farwell to all your files, to say the least.
Meh, I don't have any data worth saving, so that's no biggie... I just want to root this damn phone...

Categories

Resources