[SOLVED] downgrade from stock ics to stock gb -> stuck at bootscreen - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

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

Related

[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] i9000 Black screen of Death, But can get into DL Mode

Hi Guys, I have a SGS i9000M, and I used this forum post http://forum.xda-developers.com/showthread.php?t=1379650 to install CWM and ICS 4.0.3. I also installed Semaphore Kernel 1.2.0. It was working great for a month until I was messing with the Semaphore settings and enabled Bigmem, then when I rebooted it was stuck on the Semaphore Kernel screen, I couldn't get into CWM, but I could get into Downloading Mode.
I Run Odin 1.85 and select my I9000UGKG3-homebinary.tar file to go back to stock and when I do, I get the message: Cannot open the specified file (Line 1876). I have downloaded 3 different versions of that file, so I know it's not the file.
I've tried every combination of buttons I can, but it's not going into CWM, I just get the black screen of death whenever I reboot any way other than into Downloading Mode.
Can anyone please help me? Thanks!
*Edit: I flashed the PIT, PDA, CSC of the JVP Rom from the above linked post, and got it going, flashed chainfire, it works fine up until then, but when I install the ICS zip, it just flashes some installing stuff, then reboots, over and over, never completing, please help! I've tried different downloads of ICS 4. To repeat: It works fine installing Gingerbread and chainfire, but ICS gets stuck in a loop during install!
I remember something similar when I first flashed to ICS.
I just popped the battery out for a bit, not too long, and then re-flashed the ICS ROM. I was using the teamhacksung rom.
You could try flashing cm9 nightly (galaxysmtd), and Google Apps, and the cm7-kg3 modem.
I can't emphasize enough that you have to read, read, and re-read so that you do it exactly as written. There are lots of youtube videos that may aide you seeing what the "word instructions" mean.
Persist and you will get there.
As the the op says in the second thread of the link you quoted:
if your upgrade to ICS fail
do not despair...
just repeat the Odin steps to get back to KG3 stock + CWR
and flash another ICS build
A further thought may be that you do a factory reset at the beginning of your process. Make sure anything precious is saved to your external sd card.
Hi there, thanks for your reply. I will try your suggestion of the factory reset at the beginning. *Edit: tried, and same problem. When I go to flash stock rom I9000UGKG3, error Line 1876.
The problem i'm having is I can't flash back to KG3 stock, when I try to flash I9000UGKG3-homebinary.tar file to go back to stock, I get the message: Cannot open the specified file (Line 1876). All I can do is load the JVP rom. I have tried multiple different downloads of my I9000UGKG3 stock rom.
I've left the battery out overnight, and tried to flash all different versions of ICS multiple times. I do agree with the 'try again and wait' theory that goes with this stuff, because it works, but in this situation, it gives me the same error 1876 every time, I can't flash back to stock. That might be why I can't install ICS.
I was able to do all of this first time before and ran ICS 4.0.3 with Semaphore Kernel for a month before I messed it up.
Anyone know any other ways to get back to stock?
Thanks!
Hi,
Here some stuff I had in my notes, I'm just copy/pasting, excuse the repitition.
Ditch the i9000m stock rom (which is UGKG3 2.3.3, the one you're probably using) and flash JVT (2.3.5) stock rom, then flash CF-root for JVT. The Bell i9000m will run on the International i9000 firmware and this should get you out of the bootloop.
http://forum.xda-developers.com/show....php?t=1102881
Follow the instructions on here. Use the JVT 2.3.5 PDA, KG3 modem, and csc...its the canadian one. And you might as well repartion with 512 pit. All this can be downloaded on the link above. After you do all that you will have the latest gingerbread firmware. Now you can root with a JVT kernal like semaphore or CF root. There are also a bunch of custom roms you can use on JVT not much if anything for I9000m . The only thing you need from I9000M is the modem and csc....otherwise your cell coverage will suck. I assume you already have odin, if not its available on the above link aswell.
I remember ODIN flashing JVU before going to ICS. Just wanted to see what the value pack was all about.
PDA - use JVT/JVU
Phone - KG3
CSC - KG3
PIT - 512
Re-Partition - ON
Auto Reboot - ON
F. Reset Time - ON
---------- Post added at 01:47 PM ---------- Previous post was at 01:36 PM ----------
Here was something else in my notes:
Recovery
Mounts and storage - Format cache, data, and system
Flash stock
Hiya, thanks again for your reply. I also live in BC, Vancouver.
I will try your further suggestions, thanks so much for sharing your notes.
The link included seems to be dead, any chance to find the thread it would have pointed to?
Cheers.
Here it is:
[Firmwares]Official I9000/I9000M Firmwares collection [Latest: XWJW6, XWJW5, XXJW4]
I'm in Kelowna-fornia.
fixed - ICS install issue
That's sweet, Kelowna is a nice area :>
Well, I worked my butt off for almost two weeks, 4 hours a night.
I should start off by saying I still cannot boot to Clockwork Recovery with any button combination, i've tried all the usual suspects and then some atleast 50 times, probably way more. The only way I can is once in awhile a miracle occurs and it reboots to Clockwork Recovery 5 (the blue text themed one), or if I install CF-Root and use to reboot into recovery in it's options.
I should also mention that whenever I do get into Clockwork Recovery, it's like version 3, with the orange text theme. And I don't know if it helped, but I am now using Odin 1.87 instead of 1.85.
I was finally able to flash stock by flashing the 4 separate files, 512 Pit, PDA, Phone, and CSC rather than flashing the UGK3homebinary.tar.
I tried multiple different versions of Gingerbread with CF-Root to try to get ICS or CM9 working, JVT, JW1, JVU, all of them worked, but the same thing happened when going to install ICS, and even CM9, the install would start, once it got to the part where it says "Rebooting if necessary" on the ICS or CM9 install, it would reboot, show the install beginning again, then reboot at the same spot, infinitely. I made sure to try atleast 50 times so I could bypass the suggestion of trying again.
During this process the phone was acting very buggy, you know what I mean, restarting, freezing, force stops, mounting storage issues. I went into the options and set the phone to factory default, also during another miracle one time it booted to the stock android recovery, you know the one with like 4 options. Format, Wipe, go back, reboot. I formatted and wiped from there as well. These two things seemed to help alot, and the phone was less buggy and more willing to receive my treatments.
After browsing some more, I found this kernel cleaner, i'm surprised no one in the forum mentioned it to me, perhaps they were angry I hadn't discovered it on my own. In any case it's called 'Ultimate Kernel Cleaning Script - 4.0 [MIUI/CM7 and SAMSUNG]', there is one for Samsung Roms and one for CM roms, and all you do is run it to clean out the old before installing ICS. Link: http://forum.xda-developers.com/showthread.php?t=1166954
Ok, so I am now I am excited, this tool looks like my answer. I flash stock, install JVT rom with CF-Root for JVT, (I run my sweet kernel cleaner zip I found) and go for ICS 4.0.3 install.....and same thing happens, sigh. Flash stock again, and oh what's this? I found another custom ICS Rom I can try, remICS http://forum.xda-developers.com/showthread.php?t=1687727
Ok, so I flash stock again, install JVT, CF-Root for JVT, install remICS and....D'oh! Same thing, it's rebooting........but wait, this time it's rebooted into Clockwork Recovery 5 on it's own without any keypress, instead of looping. What a great time for that Miracle! (This only happened 3 times in about 60 hours of working on the phone!) Ok, but what to do now? Well, ICS didn't really install, it just started to, maybe i'll try to restart the install from in here! Choose install zip, this time I chose remICS only because so far it had the lesser fail rate - I didn't want to mess up this golden opportunity, I know it's just a different version of Clockwork popping up, but when anything different than the same failures happens, you don't want to waste it. It's installing....complete! Do I dare risk installing a customer kernel and destroying all of my progress? Yes! Install Semaphore 1.2.6 for ICS, working great!
So, I don't know if it was the kernel cleaner, the remICS, or the miracle Clockwork 5 boot, but I don't want to take anymore chances, that's how I got here, fiddling with what's working great already.
I probably didn't need to post this, but I wanted to recount my experience for anyone else having a similar problem. I have now been running stable with all my apps installed for 12 hours. I would like to have stock ICS with phone rooted, but I don't want to take any chances. This remICS custom rom is very nice, speedy and alot of the bloatware removed, along with some killer SGS3 menus and layout.
I would like especially to thank my Canadian friend for helping me :victory:

[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] Bricked Gnote, no experience on the field

so i have been running Paranoid android for a while, and wanted to try this out:
http://forum.xda-developers.com/showthread.php?t=2051904
flashed the latest cm10.1 kernel, and then formated cache, dalvic, battery stats, etc.
then i managed to reboot before i had flashed the new rom and got stuck in bootloop. could not access CWM any more
after this i downloaded odin after a few forum reads, and flashed different versions of CWM to see if i could get back in to flash the rom.
the latest one i have in it is this:
http://fs1.d-h.st/download/00033/pQK/GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar
as it was recommended in some un-brick thread. still no access to CWM
after this i flashed a stock rom, as i could not find any .md5 or .tar roms to use with odin, and i got at least a samsung logo on hte screen, before i got back to boot screen and was stuck there again.
CWM still not working, or showing up in any way.
out of obvious options i now tried flashing the pit file trough odin from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
and after this the samsung boot logo did not show up anymore. only boot loop
i am now going to try and download the older ginger bread rom and flash it trough odin, but i got no idea if it will make any difference.
otherwise phone goes to download mode just fine, and i got working drivers in windows trough kies.
im quite new to this, and dont really know what would work from here. ill end up hard bricking the phone if i don't get some help, and the trash can will be my n7000 next home.
any advice is welcome
--------------------------------------------------------------------
EDIT:
flashing official rom again after the pit file acrually gave me a working phone again. also i now got 50 gb of drop box storrage for free, so thats nice

Categories

Resources