Help - Bootloop from format sdcard, odin didn't fix - Galaxy S I9000 Q&A, Help & Troubleshooting

Here is my situation:
Flying to Europe long-haul tomorrow and I have no phone. I was about to swap phones with someone, so I cleared the data (factory reset) and formatted the sdcard , I didn't think this would delete my whole ROM and recovery image, just some nude pictures I needed to remove.
I was stuck on the boot logo (samsung .Galaxy S.. GT-I9000), which would flicker every now and again as it restarted.
I used to have Slim ICS 4.2 and Clockwork 5.x (I think), but I just want to have a working phone for my travels.
Now I have the yellow triangle working. With ODIN I have even managed to get a simple recovery, but it still boot loops, albeit with an fancier animation and optus logo.
Odin settings:
PIT: s1_odin_20100512.pit and
PDA: JW6_JV6_JW1.tar
re-partition: yes
auto-reboot: yes
f. reset time: yes
odin3 v1.85
So is there an odin compatible ROM around that will actually work for a blank sdcard? It's an Australian GT-I9000 from optus.
I think I'm close to getting this thing working, but having a flight tomorrow I don't have the time to search for roms.

I now have a working phone after flashing JVT from here http://forum.xda-developers.com/showthread.php?t=1583026
Can't wait to get this samsung junk off it and get back to Slim ICS.

Odin on a Semaphore kernel from the dev thread onto your phone (.tar file). Preferably use version 1.2.6 from the ICS thread. Boot into recovery mode and use the format SD card option there. Stick with 2 GB and 0 MB allocated to swap. After that finishes mount the SD card from CWM and copy a ROM onto the phone, then flash it. CM9 or 10 should be fine. Alternatively you can Odin a stock ROM back onto the phone.
Sent from my Nexus 7 using Tapatalk 2

Hey
You need to un-check the repartion in odin3...dat creats bootloops..
That would have been the issue...
Cheers
If my post helped, dont forget to hit the thanks button..

reflash stock froyo it will surely help you just make sure u put correct files on their correct places

Related

[Q] How to revert back to stock JPB after custom ROM and get rid of CD-ROM device?

Hi,
I need some help from you regarding following issue.
Lately I've loaded Darky 8.1 on my SGS, before I didn't use any custom ROM, nor rooted my device.
Few days later I decided to go back to stock froyo.
I flashed the phone via Kies with reg patcher set to SER (that's the original product code I had), and loaded JPB.
Now, when I connect the phone to PC, there appears a CD-ROM device in addition to internal and external cards. I've tried it on different PCs, the drive still appears.
I then flashed the phone once again, but this time via Odin with re-partition ticked, and 512 pit selected. No change.
Sure, I've made a wipe, formated internal card, deleted cache after each flash.
My questions are:
1. What I did wrong?
2. What does the re-partition option mean in reality? Does it delete all the internal partitions and create them again?
3. Is there any chance, that Darky's ROM changed something irreversible in the system, that cant' be fixed with simple firmware upgrade like I did?
4. Does 8.1 version by any chance touch bootloader or efs partitions during upgrade?
Btw, I never used any lagfixes.
Your comments are welcome and appreciated!
I would ask Darky if its his rom .More fu ups on this rom than any other .
http://forum.xda-developers.com/showthread.php?t=818556
And take it back to stock Eclair then update via Kies .
jje
JJEgan said:
I would ask Darky if its his rom .More fu ups on this rom than any other .
http://forum.xda-developers.com/showthread.php?t=818556
And take it back to stock Eclair then update via Kies .
jje
Click to expand...
Click to collapse
It is pretty easy. I suppose that you have ClockWorkMod recovery, which is installed automatically with Darky's ROM.
Then just reboot to Download Mode, connect your phone to the PC,
and download JPB firmware. Password for that RAR file is samfirmware.com
Once extracted, startup Odin, and flash. You can use my howto, to find out howto use Odin to flash your phone. Once done, phone will reboot itself.
Reboot it to the recovery again, and select reformat internal SD-Card menu item.
After another reboot, you will have clean, factory-set phone, like you had in time when you have bought it.

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]

[SOLVED] downgrade from stock ics to stock gb -> stuck at bootscreen

hello,
i bought a fresh n7000 with stock ics firmware on it. i wanted to go to paranoid android.
1. i rooted the stock ics
2. found out that i need gingerbread to flash custom firmware
3. installed sdk, driver on ubuntu
4. installed heimdall, as its the odin for linux
5. downloaded N7000XXKJ4 from samfirmware.com
6. extracted it to have the single images to flash with heimdall 1.3.1
7. booted in download mode, attached the phone to usb and hitted detect device in heimdall
8. device was found
9. started flashing, first without repartition
boot.img as BOOT
param.lfs as PARAM
factoryfs.img as FACTORYFS
cache.img as CACHE
zImage as KERNEL
Sbl.bin as SBL1
hidden.img as HIDDEN
modem.bin as MODEM
10. flashing went all thru, the phones screen showed the progress also
11. phone did a reboot, after all flashing was done
12. stuck at bootscreen
13. found in the web that its normal and i should do a factory reset in the recovery (its not cwm)
14. stuck at bootscreen
15. repeated step 9. with pit file and repartition
16. same bootscreen
i know the phone is not dead, just not booting, but i have absolutely no chance to find out what to flash exactly and how to do it.
hm could i now just flash the abyss kernel and cwm recovery.bin or so and install a custom rom?
if you are now on GB then flash a kernel, either in CWM or odin and do a full factory reset along with all caches and dalvik cache.
i wouldnt recommend flashing a custom ROM until the stock rom is booting, you dont want to be covering up any underlying errors.
Also, Why did you re-partition ? Did you re-partition using a 3 file firmware (PDA, CSC, Phone) or just a single firmware - PDA ??
hm i dont know on what i am, because it doesnt boot.
i thought i eventually had to repartition because i changed from 4.0 to 2.3.5 ... i used the n7000 16gb pit file.
Well what did ODIN say ? Did it complete or did it get stuck and fail ?
You can flash a kernel in ODIN which should allow you to enter CWM and do a wipe, However you might get issues if you flash a GB kernel over ICS Firmware and vice versa
heimdall ran complete through, said its all fine and the phone rebooted at the end of flashing as it should be. seems all perfect.
the issues i get can not be worse?! if i would now flash a gb kernel, even if there is ics under the hood, the phone would also just not boot?!
I dont know really, Ive never tried, nor do i intend to lol.
But i imagine GB is now on your phone considering it all passed without fail So i guess you should try to flash a kernel and then do a full wipe and see if it boots then
chances are there are some ICS files left on the system preventing it from booting.
and following the guides on xda im not allowed to flash the other kernel with heimdall/odin.
i should use the cf-kernel for my firmware and flash it with the bat-script, is this correct?
Just flash this in ODIN and you will be fine
https://dl.dropbox.com/u/69014495/GingerBread-speedmod-kernel-n7000-k2-12-Odin.tar
boot into recovery, do a factory reset, then clear cache partition, then go to advanced and clear dalvik cache, then reboot
then report back
ok. now i have the yellow triangle. i wanted to avoid this.
BUT it looks very promising. clockword mod is starting. did the wipes. and when i reboot it boots directly in cwm. i think this is good atm.
i have to leave at work now. tomorrow morning i can flash a rom with cwm right? and if i flash an ics rom, then i have to flash a ics kernel, too?!
Dont worry about the triangle, Use this app to remove it https://dl.dropbox.com/u/69014495/eu.chainfire.triangleaway-47fe5bbd55070e4eddce741c0ef13110.apk
Like i said above, Make sure the phone boots before flashing any other ROMs. If you want to upgrade to ICS you will need to flash ICS in ODIN, Unless you want to use a CM9 / AOSP based ROM like Paranoid Android, In this case you will stay on GB, Just full wipe and flash ROM in CWM
EDIT: I mis read your post, Your phone is not booting, But only booting into CWM, In this case, try a custom ROM, Nothing to extreme just a simple GB ROM and see if it boots properly then
thanks so much!
flashed checkrom notehd via cwm. boots clean and nicely up.
i flashed/rooted some phones before htc hero, hd2, zte blade. but none of them, even the hd2 with its windows conversion was as unclear as the n7000. i think because in former times the developers wherent as many as actual, and there were much less guides/tuts/howtos which made an user less unsecure.
nevertheless, your support is gorgeous: friendly, fast and ultracompetent.
edit: can i change the title in solved anyhow?
xmaskx said:
thanks so much!
flashed checkrom notehd via cwm. boots clean and nicely up.
i flashed/rooted some phones before htc hero, hd2, zte blade. but none of them, even the hd2 with its windows conversion was as unclear as the n7000. i think because in former times the developers wherent as many as actual, and there were much less guides/tuts/howtos which made an user less unsecure.
nevertheless, your support is gorgeous: friendly, fast and ultracompetent.
edit: can i change the title in solved anyhow?
Click to expand...
Click to collapse
Your welcome!
Glad to see you're up and running again
Oh and if you go to your very first post on this thread, Click edit then you should be able to put [Solved] in the title bar
Buddy start from crap...and one advice..u never know the depth of an ocean unless u dive into it..be brave...just follow cursed4eva tutorials on youtube.u will know everything...and only u can teach uraelf no one else..what i did when i was a boy,i mean when i was new to note,i followed this guy and he saved my daymy recommendations is to use odin...flash a 3file rom whose links are provided in cursed4eva's video..and flash it...u will be on stock gb..
Sent from my GT-N7000 using xda app-developers app

[Q] HELP! bircked note

hello everyone
my friend bricked his note and i don't know what to do for him, my friend has no exper experience, he did a restore on a nonsafe kernel
his phone is semi bricked (if not fully bricked), i tried using odin to flash a stock rom (gb then ics) but had no luck and proccess stops at "NAND write start", i tried only to flash a kernel which was abyssnote but also got stuck on "NAND write start" and i tried to use the pit file from this post (http://forum.xda-developers.com/showthread.php?t=1667886) with a stock rom and with re-partition checked on odin and now it is stuck on:
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
please help me as the phone has been stuck on this state (pit file way) for over 80 minutes
waiting for your answer...
i unpluged my phone now and i am trying a custom pit file (N7000_16GB_Q1_20110914--patched--brick-between-281-and-3770-MB--FACTORYFS-moved-by-3328-MiB.pit) after leaving my phone for up to 2 hours and with no progress using N7000_16GB_Q1_20110914-stock.pit
file, hope i can revive my friend phone and please try to point me for any solution i can try.
Check your connection. Usually if bricked the process will start ok but halt at factory.fs. Try with a different usb cable, make sure it's in a mobo usb port not front one.
Pit files should be a last resort. I don't think it's bricked personally. Does it power on at all?
Sent from my GT-N7000 using xda app-developers app
SpyderTracks said:
Check your connection. Usually if bricked the process will start ok but halt at factory.fs. Try with a different usb cable, make sure it's in a mobo usb port not front one.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
how can i use mobie odin if i can't even access phone nor recovery?
hope there is a way
darkelfa2 said:
how can i use mobie odin if i can't even access phone nor recovery?
hope there is a way
Click to expand...
Click to collapse
Yeah, edited afterward.
Sent from my GT-N7000 using xda app-developers app
come on people... there most be someone who knows what i should do, please help
SpyderTracks said:
Check your connection. Usually if bricked the process will start ok but halt at factory.fs. Try with a different usb cable, make sure it's in a mobo usb port not front one.
Pit files should be a last resort. I don't think it's bricked personally. Does it power on at all?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
when odin get stuck on nand write start, the box above the port number with yellow mark says factoryfs, and yes the phone can olny boot to download mode
darkelfa2 said:
when odin get stuck on nand write start, the box above the port number with yellow mark says factoryfs, and yes the phone can olny boot to download mode
Click to expand...
Click to collapse
What is the outcome of flashing the "N7000_16GB_Q1_20110914--patched--brick-between-281-and-3770-MB--FACTORYFS-moved-by-3328-MiB.pit" as you mentioned above?
If you can also get into recovery, then better try to use hg42 partition scanner first, to see if and where the damage is in the emmc.
http://forum.xda-developers.com/showthread.php?t=1823918
forest1971 said:
What is the outcome of flashing the "N7000_16GB_Q1_20110914--patched--brick-between-281-and-3770-MB--FACTORYFS-moved-by-3328-MiB.pit" as you mentioned above?
If you can also get into recovery, then better try to use hg42 partition scanner first, to see if and where the damage is in the emmc.
http://forum.xda-developers.com/showthread.php?t=1823918
Click to expand...
Click to collapse
phone been on odin for about 40 minutes or so (is that normal?) but stuck on set partition and as i mentioned above, i cant access my phone nor recovery but i can access download mode.
darkelfa2 said:
phone been on odin for about 40 minutes or so (is that norma?l) but stuck on set partition and as i mentioned above, i cant access my phone nor recovery but i can access download mode.
Click to expand...
Click to collapse
If that long, then that pit doesn't seem to work.
I would try to flash a custom kernel such as hydracore or some other kernel that are available in .tar format. Then see if it help the phone get into recovery.
If that does not work, then just need to try other pit file from hg42 thread which move factoryfs by bigger number until it work. This is not a good strategy but it seems to be the only way.
---------- Post added at 11:29 PM ---------- Previous post was at 11:19 PM ----------
This is a gb kernel that can be flashed via odin to see if recovery works.
http://www.mediafire.com/?smwswkxwa3u3p4s
forest1971 said:
If that long, then that pit doesn't seem to work.
I would try to flash a custom kernel such as hydracore or some other kernel that are available in .tar format. Then see if it help the phone get into recovery.
If that does not work, then just need to try other pit file from hg42 thread which move factoryfs by bigger number until it work. This is not a good strategy but it seems to be the only way.
---------- Post added at 11:29 PM ---------- Previous post was at 11:19 PM ----------
This is a gb kernel that can be flashed via odin to see if recovery works.
http://www.mediafire.com/?smwswkxwa3u3p4s
Click to expand...
Click to collapse
i got stuck on NAND write start agine, i think its time to try your other strategy, should i go with pit file that has factoryfs moved by the largest number first or the one with the less number?
darkelfa2 said:
i got stuck on NAND write start agine, i think its time to try your other strategy, should i go with pit file that has factoryfs moved by the largest number first or the one with the less number?
Click to expand...
Click to collapse
I would try the first way of flash a kernel since it does not take much time.
Anyway, if want to try second strategy should move up by 500 mb or 1 gb each time.
I saw some people reported problem after flashing a pit with big number them move back to flash a pit with small number so should try to avoid that situattion.
The next pit I would choose it the one move fatoryfs by 4608mib for example.
forest1971 said:
I would try the first way of flash a kernel since it does not take much time.
Anyway, if want to try second strategy should move up by 500 mb or 1 gb each time.
I saw some people reported problem after flashing a pit with big number them move back to flash a pit with small number so should try to avoid that situattion.
The next pit I would choose it the one move fatoryfs by 4608mib for example.
Click to expand...
Click to collapse
thank you for your replies, i will try to try them as you mentioned above and by the way and will wait 15-20 minutes in each operation, i already tried the last version of hydracore but had no success, one last thing, if none of them worked (hope not), is there any other possible way to revive from the brick(other than replacing the motherboard or replacing the phone from samsung)?
bricked or not
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.
sahil4u said:
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.
Click to expand...
Click to collapse
it is good as far as you can access cwm recovery, try to get any external sd, download a rom and put it on the external sd using other phone
and flash it using cwm and dont forget your safe kernel , and can you tell me please what kernel you've used?
sahil4u said:
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.
Click to expand...
Click to collapse
Once get recovery it is best to try to scan partition to identify where the damage is. You can you adb method in my manual repartition guide or the scanner from hg42 which is even better.
Sent from my phone
---------- Post added at 06:30 AM ---------- Previous post was at 06:25 AM ----------
darkelfa2 said:
thank you for your replies, i will try to try them as you mentioned above and by the way and will wait 15-20 minutes in each operation, i already tried the last version of hydracore but had no success, one last thing, if none of them worked (hope not), is there any other possible way to revive from the brick(other than replacing the motherboard or replacing the phone from samsung)?
Click to expand...
Click to collapse
Should try the kernel I sent and also the fm kernel suggested in the post above. Once having recovery it is much easier and there are more options. Otherwise, custom pit is the last resort before mobo replacement.
Sent from my phone
sahil4u said:
same problem here, was on stock ics rooted for quite sometime, today decided to flash alliance rom v2.1, booted to cwm recovery, did a full wipe and after that i just hated myself. phone didnt boot into recovery and odin gets stucked at factoryfs, tried to flash with pit file too but no result same stuck in problem. then i flashed different kernel fm note kernel through odin which was a success, got my recovery back but unfortunately the only rom i have on internal sd was alliance rom which doesnt install, either says emmc error alliance rom or stucks at extracting system. so again flashed abyss kernel and did a full wipe again but odin still does not go beyond factory fs and i am trying to flash ics rom again. any idea what i should do now as i can flash a kernel and go into recovery. help will be appreciated. meanwhile downloading gb rom to check as i read in other posts it works tough not sure.
Click to expand...
Click to collapse
Hi there, sounds like a bad flash or bad download. Firstly remove your external micro SD card and connect it to a PC / Laptop (standard SD adaptor or Card Reader). Download a "default" ROM and kernel and KEEP them on the card (you never know when you need to go back to them). I use Abyss 4.2 kernel and Chrack ROM personally. I always have the jBroid Kernel Cleaner saved also). Replace the micro SD card.
If you can get into Recovery, flash the jBroid script cleaner. Now flash Abyss 4.2 kernel (GB safe kernel) and reboot into Recovery again. Now flash Chrack Rom. I've had a number of bad flashes and these 3 zips have always pulled me out a hole.
Hope this helps. Hit Thanks if it did.
Alba Donzo said:
Hi there, sounds like a bad flash or bad download. Firstly remove your external micro SD card and connect it to a PC / Laptop (standard SD adaptor or Card Reader). Download a "default" ROM and kernel and KEEP them on the card (you never know when you need to go back to them). I use Abyss 4.2 kernel and Chrack ROM personally. I always have the jBroid Kernel Cleaner saved also). Replace the micro SD card.
If you can get into Recovery, flash the jBroid script cleaner. Now flash Abyss 4.2 kernel (GB safe kernel) and reboot into Recovery again. Now flash Chrack Rom. I've had a number of bad flashes and these 3 zips have always pulled me out a hole.
Hope this helps. Hit Thanks if it did.
Click to expand...
Click to collapse
i've already mentioned that it has no recovery mode, and yes, i always have abyssnote kernel in my ex-sd also in my friend's phone, the thing is that he don't know about the emmc bug and he did a restore on a none safe kernel and thats how he bricked his phone
what i've done so far is trying the pit file way but had no luck, now the thing is that the binary counter is 5 and i can't go to have a m/b replacement for free as the warranty is voided, is there any way to reset the counter or to hardbrick the phone except for the jig method?

[Q] Soft Bricked N7000

I was trying to install Ultimate_N7000_LSC_JB_4.1.2_v5.1 on non-rooted device.
After booting into Recovery and installing CWM, i tried Data wipe/Factory reset.
(Battery was 100%)
The screen switched of suddenly and now i am stuck.
Here are somethings i have tried:
1) Tried flashing N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 using ODIN. Never goes beyond NAND flashing (Tried in Admin mode, with ODIN Mode)
2) Tried flashing cm-9.1.0-n7000 and had status 0 and status 7 error many times.
Most of the flashing methods mention : "wipe data/Factory reset". Whenever i do that, i get stuck in "Wiping Data... .Formatting /data"
I have tried "Fix permissions", it wont work.
I didnt take a ROM backup and now i really regret it.
Currently when i navigate using CWM i can see all my internal as well as external memory files. So, i guess my OS is gone and files are still there.
The Custom Rom Counter says: Yes (Count 4) in ODIN mode.
Can someone help ? Please i am desperate.
What rom you on before flashing?..GB or ICS?
Sent from my GT-N7000 using Tapatalk 2
ICS 4.0.4
I had not done any Modifications, rooting to my N7000 before yesterday.
Would like to go back to Any ROM.
Unrooted ROM (ICS 4.0.4), Leaked JB Rom, CM9, CM10. Any ROM. Just want to get my phone up and running
What error do you get when flashing with Odin?
Does it stop at "factoryfs.img"?
How did you install CSM on your stock Rom ICS 4.0.4?
Your "soft bricked" sounds more like "super bricked" to me.. Did you use CWM.zip to wipe?
Tapatalking on my n7000
Yes. I used CWM.zip.
But now that my phone is not working, how do know what is the firmware version?
(http://forum.xda-developers.com/showthread.php?t=1656635)
Can you tell me the exact file names i should use
PDA: CODE_N7000xxxxx_CL627135_REV02_user_low_ship.tar.m d5
PHONE: MODEM_N7000xxxxx_REV_05_CL1067428.tar.md5
CSC: GT-N7000-MULTI-CSC-Oxxxxx.tar.md5
What does xxxx stand for? I have the Serial No. of my phone. And have done normal OTA updates only.
Brought from flipkart in August (if it helps narrow down the xxxx)
Superbricked or soft, please help.
Just downloaded some CWM file (Sorry i searched a lot, i couldnt remember the source)
Here are the steps:
Flash it with Odin 1.85, (Click PDA, choose the file and press Start)
After this you will have Root on your phone.
Now you can go into CWM and flash the Rom.
1) Download Ultimate XXLSC Jelly Bean 4.1.2 custom ROM for Galaxy Note to the PC
2) Connect the device to PC using USB cable and transfer the downloaded ROM zip file to the phone's SD card
3) Unplug the USB cable from the phone and then turn it off
4) Enter into Recovery mode by switching on the phone while pressing and holding Volume Up, Home and Power buttons together
5) In CWM Recovery, perform a full data wipe
Here is where it suddenly stopped and the screen went blank. (I am double sure battery was 100%)
Thanks for the prompt replies
Yup..its a wrong way to flash costum rom on stock ics...
try flash stock rom using odin, if its stuck on "factoryfs.img".. I'm sure your super bricked your phone..
Sent from my GT-N7000 using Tapatalk 2
zai89 said:
Yup..its a wrong way to flash costum rom on stock ics...
try flash stock rom using odin, if its stuck on "factoryfs.img".. I'm sure your super bricked your phone..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
ok. But please help me. How to take it out of super-brick.
In ODIN it gets stuck in "NAND write start"
I already tried flashing Stock ROM N7000DDLRB_N7000ODDLR4_N7000DDLR1_HOME.tar.md5 in ODIN and it gets stuck in "NAND write start"
I found this post. http://forum.xda-developers.com/show....php?t=1656635
Should i follow this?
Can you tell me the exact file names i should use
PDA: CODE_N7000xxxxx_CL627135_REV02_user_low_ship.tar.m d5
PHONE: MODEM_N7000xxxxx_REV_05_CL1067428.tar.md5
CSC: GT-N7000-MULTI-CSC-Oxxxxx.tar.md5
What does xxxx stand for? I have the Serial No. of my phone. And have done normal OTA updates only.
Brought from flipkart in August (if it helps narrow down the xxxx)
(Thanks in advance)
If you have warranty then claim it.. Super brick means that the emmc chip it's burned.. There's some methods to get it to partially work but you lose around 3Gb of memory and generally you can not use TW roms.. Or at least stock TW.. Not to mention the random reboots and freezes..
So most likely if you don't have warranty then use the pit file method or pay for a motherboard replacement..
Tapatalking on my n7000
Thanks for the suggestion.
I managed to flash 4.0.3 ROM and stock Kernel and it somehow worked. (did too many things)
Here's the current status: Running 4.1.2 (XXSLO, ZSLM5). Unrooted and stock ROM. (Updated from 4.0.3 to 4.1.2 in kies)
Everything is back. The phone runs good. But when i try installing any software, it will freeze. The apk/app installs eventually but after 2-3 reboots.
Can you tell me the issue?
I read it somewhere that the "Cache" partition is damaged.
Can someone please tell me any way to avoid freezes.
msedek said:
If you have warranty then claim it.. Super brick means that the emmc chip it's burned.. There's some methods to get it to partially work but you lose around 3Gb of memory and generally you can not use TW roms.. Or at least stock TW.. Not to mention the random reboots and freezes..
So most likely if you don't have warranty then use the pit file method or pay for a motherboard replacement..
Tapatalking on my n7000
Click to expand...
Click to collapse

Categories

Resources