Database Develop

Solution JPM Not Prepared your storage yet, please use UI menu for format and reboot

On first boot I get
Can not mount / dev/block/stl10 (Invalid argument)
copy_dbdata_media: Can not mount DBDATE
Not Prepared your storage yet, please use UI menu for format and reboot actions
default copy content failed half
wiping / data cache and Does not Seem To fix anything.
Format sdcar unresponsive
HELP any occurrence and brick my phone

criskelo said:
On first boot I get
Can not mount / dev/block/stl10 (Invalid argument)
copy_dbdata_media: Can not mount DBDATE
Not Prepared your storage yet, please use UI menu for format and reboot actions
default copy content failed half
wiping / data cache and Does not Seem To fix anything.
Format sdcar unresponsive
HELP any occurrence and brick my phone
Click to expand...
Click to collapse
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help

sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
Fixed in a while I explain

My solution
With Odim 1.3, pit 512,
in my case JH2 I9000T GT
But for Europe JM8
Mark Re-partition, phone EFS clear and Phone bootloader Update
Then start
This process started well
JPM Process
Then uncheck re-partition, phone EFSclear and Phone Bootloader Update
JPM Pit 803 and firm JPM
Start
To enjoy
Thanks

criskelo said:
Then uncheck re-partition, phone EFSclear and Phone Bootloader Update
Click to expand...
Click to collapse
Is it normal for T model, or you just use weird and dangerous settings for fun?

Wiping EFS can lead to test-imei number and broken product code. Be sure you haver a backup of that folder before wiping that.

criskelo... I tried this and I didn't get anywhere :/

I had the same issue and it took me 2 hours to resolve (with a lot of pain, lol).
I've simply flashed the XWJM8 version using odin 1.3, no pit file and HENCE no repartition ticked.
It then booted to recovery console, because there was another error (can't remember which one cause I was too excited).
Anyway I did a wipe, cash clear and reformat SD card at the menu and let it boot.
After that I have flashed the latest version XXJPY also without PartitionInformation Table. (PIT). Then all the wipe and format stuff again.
I have now to go from scratch to setup anything again, but hey, at least my phone is alive again.
Some additional info. I also had that connection symbol on the screen with exclamation mark and triangle....so I thought I was done (due to trials with pit 512 which hung), but after removing battery and some trials I was able to enter download mode again....
Why happened that? I DON'T KNOW! I simply wanted to reflash the XXJPY stock rom, this time with pit512 and it lead to the topic of this thread!!!
This su**ed a lot, I didn't even modify something before!!!!
So: Less is even more! Don't fiddle with EFS and bootloader options it worked for me even without a pit!
Thanks to sardor for the initial idea, the XWJM8 seems to be a fixing rom for that when used properly, anyway to load a pit without to tick repartition is not a useful setting!
Well I was a long time reader at this great forum, IMHO the best regarding phone stuff, because there is the most useful knowledge shared.
I hope my first post will save other phones as well from sending it to repair.
Thanks I'm happy again..(let's see how long it'll last..lol...)

bricked my samsung galaxys and recoverd it
Hi I had exact same problem I totally bricked my i9000 Australian Optus version
I used
I9000DTJG4 firmware Australian Optus
With pit 512
And odin3 v1.3
Got all the files from
samfirmware . com / WEBPROTECT - i9000 . htm
Had to sign up but it’s free
However following criskelo's advice I unchecked the re partion box in odin
Even though the site above tells u to check it
And it worked
Thanks for everyone’s help on this thread.
Without you I would have had an expensive paper waited
Also the reason I got here in the first place as because I messed around with lag fix in clockwork recovery when I don’t know anything about it.
I was lucky this time but it’s really not worth playing around with things you doing understand.

sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook

Awesome, thanks buddy! I have spent too much time trying to fix this phone and it all totally pays off now!
Here is the fix for the Bell firmware:
Background info: I orginally tried the Lagfix and bricked my phone, this is how I finally fixed it...
1. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJH2
Use Phone: Modem.bin
(both files came from samfirmware, I9000UGJH2 download)
Use: 512.pit(also from samfirmware at the bottom of the i9000 page)
Check Re-Partition, Auto-reboot, F. reset time, phone EFS clear and Phone bootloader update. I know everyone above says don't but I tried their way first and it didn't work, I would recommend you do try their way first and if no results try mine.
2. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJL2
Use 803.pit
Check only Auto-reboot, F. reset time
Good luck! I hope you do your happy dance like I did!!

crazycanuckeh said:
Awesome, thanks buddy! I have spent too much time trying to fix this phone and it all totally pays off now!
Here is the fix for the Bell firmware:
Background info: I orginally tried the Lagfix and bricked my phone, this is how I finally fixed it...
1. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJH2
Use Phone: Modem.bin
(both files came from samfirmware, I9000UGJH2 download)
Use: 512.pit(also from samfirmware at the bottom of the i9000 page)
Check Re-Partition, Auto-reboot, F. reset time, phone EFS clear and Phone bootloader update. I know everyone above says don't but I tried their way first and it didn't work, I would recommend you do try their way first and if no results try mine.
2. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJL2
Use 803.pit
Check only Auto-reboot, F. reset time
Good luck! I hope you do your happy dance like I did!!
Click to expand...
Click to collapse
hey how did it worked for you. Not working for me.
did you extracted the tar file? which file did you loaded into the pda tab then ?
Didnt worked for me at all

sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
you saved my phone after me corrupting internal SD! just did my victory dance though hands still shaking a bit

Just thought I would add to what got my phone back running again after having the Can't mount DBDATA error. It's a bell I9000M.
Used Odin 1.3 , Flashed Darky's resurection per his instructions pulled battery once complete, went back into download mode and flashed stock JL2 with Odin , re-partition un-checked and no Pit file and after that my phone was running again.
You can find Darky's Resurection Here!
Can not find the link for the JL2 stock rom but it's in the general section somewhere.

the xxjpu version worked for me
tlick repartition
add 512 pit
tick and add pda
tick and add modem
tick and add csc
go to download mode
connect usb
press start

Need help with Fascinate
Hey guys, I've read the above posts but frankly it's above my skill.
Some how I ended up with the same message that the OP got.
Can someone walk me through the steps to completely fix my phone and get it back to bone stock?
I'm not familiar with PIT and other files. I need someone to hold me hand on this one...

cddt said:
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook
Click to expand...
Click to collapse
Was also messing around with darky. decided to go back to 9.5 for now. also got the error, then did what cddt said (thanks!!).
first flash - different error (something about CSC)
for second flash i used JS7 + 803pit + no repartitioning
worked flawlessly Thanks!

Stuck in boot loop
Samdroid_G_S said:
Just thought I would add to what got my phone back running again after having the Can't mount DBDATA error. It's a bell I9000M.
Used Odin 1.3 , Flashed Darky's resurection per his instructions pulled battery once complete, went back into download mode and flashed stock JL2 with Odin , re-partition un-checked and no Pit file and after that my phone was running again.
You can find Darky's Resurection Here!
Can not find the link for the JL2 stock rom but it's in the general section somewhere.
Click to expand...
Click to collapse
Hi,
I have bell sgs and I tried this and since then my phone is on boot loop. I can only go in download but not recovery. IT all started when I installed the boot loader for gingerbread...

Flashing Error - resolved
cddt said:
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook
Click to expand...
Click to collapse
Just followed this and it worked a treat thank you

Hi there,
I am having issues the same way. I am unable to do something. Can some explain me the procedure how to do it.
From where can i get the files.
Please help me out

[Q] Help, phone stuck booting?!

I flashed darky's rom with the voodoo lag fix and then stupidly tried to flash over the top my recovery file. now its stuck loading. can't access recovery mode but can access download mode... any ideas?

Just posted this in another thread, with similar issues, try this, should fix it.
--------------------------------
HI,
Try the following, worked for me
1) Go into recovery mode and wipe both cache and partition data
2) go to samfirmware.com and download the original rom for your phone (the one that came with it)... since you don't say what region you're from, I'll give you an example with mine. Mine is from Bell, and factory comes with UGJH2, so i downloaded that with ODIN and the PIT FILE, make sure to extract the TAR file from inside the RAR file. Put all 3 files in the same folder
3) Enter download mode, when the phone is in that state sometimes it's hard to access download, best way is... remove the battery, put it back in, then hold VOL DN + HOME + POWER until you see a working android bot inside a triangle. When you see that, connect your phone to your PC, double click on ODIN, then load the PIT file (CHECK BOX RE-PARTITION leave the others to default) and Select PDA and find the TAR file you extracted in STEP 2... then click on START, it's gonna take a few mins, and even after it's done, it's going to reboot, and it'll stay at the "S" logo for a bit, leave it, then it'll boot.
At least we hope it will.
Keep us posted,
Thank you,
Rodi.
------------------------------------

Can't get into recovery mode only download mode?! I'm on orange uk custom galaxy S Rom 2.1 originally. shall i just follow your steps but use a stock samsung android firmware?
Thanks Alot btw!

Yeah keep going with the download mode, it's very possible that the recovery mode process is not even necessary, but since I have no way of testing, it's doesn't hurt to try.
so get the orig rom, with pit associated with its (u'll see in on sam firmware which pit you need, most likely 512 for stock out of the box).
Keep us posted
Rodi

Fixed!!! flashed the new 2.2.1 firmware as well. is flying thanks for the help

alcurtis93 said:
Fixed!!! flashed the new 2.2.1 firmware as well. is flying thanks for the help
Click to expand...
Click to collapse
i have the same problem as u ..which 2.2.1 firmware did u flash and where to download ?
Cris

Dont worry mate easier to fix than I thought. Go to samfirmwares and go to firmware section and galaxy s and its called I9000 jpu. If you need any more help dont be afraid to ask
Sent from my GT-I9000 using XDA App

Heres the link.... http://www.multiupload.com/PUSOOBQ8K5
Password is samfirmware.com
Sent from my GT-I9000 using XDA App

alcurtis93 said:
Heres the link.... http://www.multiupload.com/PUSOOBQ8K5
Password is samfirmware.com
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Thanks so u much

[Q] Galaxy Ace stuck in reboot loop

My Galaxy Ace is stuck in a reboot loop after trying to flash 2.3.6 onto it, when it had 2.3.5 on it previously.
I've used ODIN and no matter what firmware I try to flash onto it, it just goes into a reboot loop.
Any idea how to fix it?

Did you try to do a wipe?

vkanamekuran said:
Did you try to do a wipe?
Click to expand...
Click to collapse
A wipe worked! Thanks!

how to do a wipe please tell

mor1228 said:
how to do a wipe please tell
Click to expand...
Click to collapse
press down home button and then power on phone ...--> you will enter into recovery mode .
select wipe with help of volume keys and there you go out of bootloop

My Galaxy Ace is also in some sorta reboot loop.
Everything was working fine with it (phone is rooted and CWM installed) until I did a phone reset because I was giving the phone to my gf. After doing this the phone reboots, the blue samsung logo plays (without sound) and then repeats ad-infinitum. I can get into recovery mode and download mode ok and I've tried wipe and even restored a CWM backup (it says it was successful) but the phone just keeps rebooting. I can see the phone in odin but I've never tried to flash anything onto it and quite frankly I'm unsure whether it would just make things worse (if it needs to go back to Samsung for repair). Any help would be appreciated...

If you have cwm ..why dont you download some custom rom like cm7and flash it ..that would bring your phone back to life ...then you can downgrade to stock rom if you want ...and btw in cwm try cache partition , clear data /factory reset and clear dalvik cache ..see if it boots after you do this ..
Sent from my SGA rocking CM7.2 by vo-1 + all-in-one script

when i always flash by odin or by cwm i always do wipe , wipe cache and wipe dalvik, this helps me everytime

I managed to flash a firmware from samfirmware and it fixed the reboot.
Now my issue is when I connect to Kies, it says there's an updated firmware for the phone but it fails every attempt to install it. I went back to samfirmware and found this firmware: S5830ZSKPD ## but when I download and extract it there's only 1 x MD5 file and 1 x DLL file?! The other firmware had the 4 or 5 files needed to include in Odin... any ideas guys?

I think its a "one package file " ..I forgot the correct name but there is some option like that in odin ..dont worry it contains all the required files ..and if you are scared to do it then go to you tube ..there are many tutorials showing it then...
Sent from my SGA rocking CM7.2 by vo-1 + all-in-one script

rogers4759 said:
I think its a "one package file " ..I forgot the correct name but there is some option like that in odin ..dont worry it contains all the required files ..and if you are scared to do it then go to you tube ..there are many tutorials showing it then...
Click to expand...
Click to collapse
Yep, that's exactly what it was, thanks again.
Unfortunately with this firmware, Kies doesn't recognise it and provides no info.
I flashed back to the older firmware... I'll just have to keep experimenting I guess.

for flashing with odin --> http://forum.xda-developers.com/showthread.php?t=1225493
many people says, don't upgrade the firmware with KIES.

dianpadi said:
for flashing with odin --> http://forum.xda-developers.com/showthread.php?t=1225493
many people says, don't upgrade the firmware with KIES.
Click to expand...
Click to collapse
Well I could flash it with Odin if I had the firmware but I don't.
It appears it's not available on SamFirmware.com
Do you know where I can download the following firmware?
PDA:KPD / PHONE:KPD / CSC:KPC (THL)
Thanks

Lol I cant understand those firmwares ..can you tell me which version of android you want like 2.3.4/2.3.5/2.3.6 ...then ill be able to help you wanr
Sent from my SGA rocking CM7.2 by vo-1 + all-in-one script

Thanks anyway but I managed to find the firmware online and flashed it using Odin.
Now Kies says I'm using the latest which is a good start : )
Now I just need to find a way to root my SGS2 GT-I9100T

U can try a custom ROM from the Developer's forums here.
I also once stucked in the Reboot Loop..............
But then I installed a custom or if you want features from a official Rom, you can install Stock Based custom ROm from the Developer forums of Galaxy Ace. Really good Rom have been made by the developers

In the chance that someone else is looking for this latest OEM firmware update:
PDA:KPD / PHONE:KPD / CSC:KPC (THL)
It can be downloaded from: http://translate.googleusercontent....flgljh&usg=ALkJrhiMpHV83dugh4RGwhKpyjIrYIgn2Q
It is in "one part file" format and can be flashed using Odin.

whatever may be the problem ......just rem to keep a backup of ur previously used rom and just flash it with cwm...

Progress?
Sent from my GT-S5830 using xda premium

Read all the previous no way out loop boot
Hi every body
i have installed cwm, custum firmware, every thing goes ok
tryed to use simlock remover, no message, turned off the Galaxy Ace but after rebooting, a continuous loop boot, no acces to recovery, flashing on wath ever firmware version with odin success but on rebooting the loop is back, help please.
PS : while flasing with odin : "big partition size!!"

Soft bricked N7000. How to?

Tried everything I could with Odin and phone still stuck in a start loop.
I was downgrading from checkROM to official firmware ZSLA2 with CWM (I wanted to keep ROOT, so I selected "Keep CF-Root kernel") due to stability issues, after restarting the phone got into the start loop.
I flashed with Odin official ZSLA2 with the same result (looped start). I flashed XXKKA (again looped start). During the flashing process, Odin says the flashing was successful. By the way, both ROMS are tar.md5 files.
I tried to remove the battery for over 30 minutes and charge it for 2 hours, tried re-partition in Odin (it's my understanding that with a stock rom, it creates a clean installation), but Odin fails to start the process.
What else can I do?
I am sorry if this has previously asked, but I've been searching for over 2 hours and nothing similar came. Somebody mentioned to use a PIT file in addition, but the other person who got his phone soft bricked didn't solve the problem either. As downloading a ROM is time consuming and I've got many problems with upload sites in china (cannot access to most of them), I would thank any help in regards this issue.

Sounds like your kernel isn't talking properly to your ROM.
A fresh start is your best bet. Flash a stock rom and kernel from Odin and reroot it with CF-Root.
What files are you putting into Odin? There should be a total of 4.
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)

I am using official ROM N7000ZSLA2_N7000ZSLA2_N7000XLA4_HOME.tar.md5 into PDA and also tried ROM N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5, which I used successfully in the past to make root into my phone.
Does it really make a difference to flash 4 separate files instead of a full pack? Where can I find an official ROM with pda radio and kernel separated? Just untar the ROM?

btyork said:
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
Click to expand...
Click to collapse
Oh, they do come into the Note; I flashed the Beta ICS, and one of the things they mention is to use the PIT file for the 16GB version, instead of the 32GB that comes with the leaked ROM. Unfortunately I deleted that ROM, and donwloading it is painfully slow and also wouldn't necessarily solve my problem as I couldn't even make a phone call.

True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.

Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.

btyork said:
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Click to expand...
Click to collapse
This are the files I am flashing:
Sorry, I am new user and still cannot post screen captures. I do have more than the 5 files.
In XXKKA I have:
Boot
Cache
Factoryfs
Hidden
Modem
param.lfs
Sbl
zImage
In ZSLA2:
Cache
Factoryfs
Hidden
Modem
zImage
btyork said:
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
Click to expand...
Click to collapse
I can only enter into Download mode, not recovery mode.
Odin is full wipe, right? What the hell am I doing wrong?

N7000xxla1_n7000oxala1_oxa
http://hotfile.com/dl/141060546/b0c7420/N7000XXLA1_N7000OXALA1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han

choihan06 said:
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you

mrfan said:
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
Click to expand...
Click to collapse
I have just recently dowloaded and installed the rom without problem. What do you mean by corrupted rom?
Sent from my GT-N7000 using xda premium

I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

Fix The problem
I had the same problem, the device got into start loop. JUST DO A FULL WIPE..! and the device should start normally. I worked for me.... :good:
Sent from my GT-N7000 using xda premium[/QUOTE]

[Q] newbie - HELP PLS - bricked?

Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty

strangermyself said:
Hi,
I came from an LG 2x, so I thought rooting my device in order to have some extra authorizations was no big deal. I first tried with pc software Unlockroot, but it failed in the process.
Being my GB 236 Note quite dirty I wanted to do some extra backup and cleanup. So I googled and stopped at rootyourgalaxynote.com, I tried the first ROOT method, not working, I tried the second method with pc ODIN 3.04 and abyss kernel 42, ODIN says it worked, note reboots but it stops at Samsung galaxy Note Gt-N7000 with yellow triangle. shocked, I didnt really expect that! After reading a little bit else, I went to sammobile downloaded italian gb 236 stock (the version I had befor kernel flashing) and tried to flash with PC Odin. It Failed. Device still gets in download mode. But now I'm seriously worried. What can I do?
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
First you should t have flash abyss through odin since now you are not rooted and do t have the warranty too, the counter of flashes increased to 1 (look at the download mode small text), for rooting you can use chainfire's tool (in the cf-root kernel thread look for it in devolepment section) next get a stock rooted kernel and flash using the tool (read instructions).
For now use pc odin 1.87 and get a firmware 2.3.6 use the pc odin select the file on PDA and flash it, make sure phone is charged 100% and press start, if it doesn't work then uninstall drivers, reboot machine, reinstall them and kill kies process if present in task manager and then goto download mode connect USB and open pc odin wait for the port to be ready aka green and select file then start.... you should be fine its a soft brick afterall.
Sent from my GT-N7000 using Tapatalk 2

Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.

strangermyself said:
Yeah I know atm I don't have system nor root nor warranty.
I tried odin 1.87 with the stock rom from sammobile but at one point or another is it cache.img or factoryfs.img, it fails (I also uninstalled kies and drivers and reinstalled them, i also tried installing only drivers, for at&at note, but it doesn't let me). I'm gonna download another stock rom, I just hope in some way I soon solve the thing, given that I also don't know how much charge is left and if the phone still gets charged. it just displays an idle circle near an empty battery when connected to pc or A\C cable.
Click to expand...
Click to collapse
When connected to charger make sure phone is off the battery meter will show as soon as you connect, case it doesnt leave it for like 3 hours is fine... next about that ROM redownload. The package cleanup you temp directories in PC and try again if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2

REVERSiN said:
... if still goto recovery abyss I guess? Wipe everything and use the mount option and format partitions I would recommed you to have repartition but I dont have the file you can look for ot in forum its. PIT file download fireup odin select it in PIT section and see if repartitioning is shocked, of so select firmware as PDA and flash again.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?

strangermyself said:
[UPDATE]: I tried using Odin 1.85 and the same gb 236 stock rom but it stops half the factoryfs.img flashing...please explain me what's happening. I don't really want to bring it in assistance and lose my warranty
Click to expand...
Click to collapse
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444

Whiskeyjack4855 said:
If you are stcuk at factoyfs.img I think you have got a super Brick
use this link and follow the instructions given.. Worked for me
http://forum.xda-developers.com/showthread.php?t=1682444
Click to expand...
Click to collapse
Dude its a GB rom not superbrick bug in it and he didn't mention LPY yet.
Sent from my GT-N7000 using Tapatalk 2

strangermyself said:
Thx for your prompt answer, but I really didn't catch this part, if it still fails I must go in recovery and wipe cache and dalvik cache?I don't have CWM installed as rooting was the first flashing I tried on NOTE, so I don't have recovery installed. Since it stopped in the middle of flashing factoryfs.img, my Note is now displaying sth like 'updrading went wrong, try recovery mode in Kies': can it help in anyway? The PIT file and procedure are the same that are used for the EMMC bug?
Click to expand...
Click to collapse
Sorry for tea doubled post its a dumb app X's
You wipe using the CWM file in the Iss root section, and a normal recovery wipe would do too (aka restore defaults)
Sent from my GT-N7000 using Tapatalk 2

Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help

strangermyself said:
Hi REVERSIN,
Thx. I was starting to fear it could be sth more than a soft brick. Can the initial use of unlockroot have caused anything (at least a week ago, Note still working after that)?
Sorry but I really can't understand what procedure should I follow since these initial attempts at flashing stocks failed. Should I try to flash CWM? What is the ISS root section (is it in the forum)? Where can i do a normal recovery wipe from? CWM I guess..
THX for your help
Click to expand...
Click to collapse
If you have the stock recovery, restore default wipes everything.
If you have stock re every and want CWM temporary just to wipe goto n7000 devolepment and check how to root by dr.ketan and get files there
If you have CWM then wipe data, wipe cache, wipe dalvik.... and try. Old download another firmware like kk5.... something else not the new LC1 LX1 releases.... (Latest GB) get an old one to get root easly
Sent from my GT-N7000 using Tapatalk 2