Database Develop

[Q] Loop reboot when installing custom roms

What i did before installing a custom rom:
I rooted my phone using superoneclick method.
Then installed xrecovery V0.1. (with busybox and charm*something)
Made a backup of the original room using Xrecovery
How did i install the custom roms and what happend:
Renamde gingerxd v13 to update.zip and place it on sdcard.
Wiped cache and factory reset(fullwipe).
Install update.zip with Xrecovery.
(after my first attemp failed, i tried to wipe cache and factory reset after installing the room too)
Reboot phone.
Phone goes into reboot loop. First sony ericsoon, then the logo of whatever custom room i'm trying to install.
I tried the MiniCM7-2.0.7 (source)
Then i tought, what if i downloader a back from another phone? i got Floyo 2.2.5 (source)
Restoring this backup too got me into a reboot loop.
Final question(and probably the supidest one if the answer is yes)
Do i need to unlock the bootloader to install a custom room? The guides i used didn't mention it at all, and since it may brick my device beyong xrecovery's help i'd like a straight answer before attempting it.
I tried to make this post as clear as possible and maybe someone can point out if im missing something.

Very important thing: Did your baseband end with 015? If no, that's why you are having these problems.
And no, you don't need to unlock the Bootloader to install Custom Roms.

It ends in 006. Thanks ill be reading on flashing a baseband and report back. PCcompanion says my phone is up do date so i'll be using this. If you have a better alternative let me know.
^^
Edit: Is there a way to configure pcc to make the update for me? Like say im from another country were the update is available?

Use Flashtool, go here

Thanks Chris95X8. my phone is now running 2.3.5 gingerdx rom. everything works. The only thing that's driving me nuts is the notification i get when i lose signal. Any way to fix this?

Sadly it didnt work for me... I have tried out flashing basebands but it wont work. still looping around. makes me crazy.

Kiwiii97 said:
Sadly it didnt work for me... I have tried out flashing basebands but it wont work. still looping around. makes me crazy.
Click to expand...
Click to collapse
Are you sure that you flashed the right baseband?
If you have, maybe try to boot phone without the SD card in it..

Erm... help?! (Odin stuck at Nand Write)

Hi all, I could really really use some help.
Today I decided to try and flash CM9 RC2 and I seem to have messed up big time.
I startred by rooting, using Dr Ketan's guide. That all went smoothly, and root was working.
I put the CM9 zip file on the SD card, turned off my phone, got back into CWM recovery, and most tutorials recommended, selected full data wipe... this is where something seemed to go wrong. While perfoming the data wipe, it seemed to freeze. I let it sit for a while, hoping it would sort itself out, but it didn't, and then it rebooted itself and went into a boot loop.
I can't get back into recovery mode, but I can get into download mode. So I thought the best thing to do would be to flash a stock firmware using odin.
I downloaded the latest german LRG firmware (which I was on before I started) from Sammobile, connected my phone to odin, selected the MD5 file, and pushed start. Again, this is where I got stuck. It just hangs on Nand write start. I've tried this twice now, and it gets stuck at the same stage (about 90% finished)
I have no idea what to do now and really need help. I'm not a total n00b, or at least I thought I wasn't, but I seem to have gotten in way over my head. What should I do?

Edit: see you tried already...
Sent from my GT-N7000 using xda app-developers app

This is classical case of super brick.
You should not hav to wipe on ics. I think u must be on stock kernel. Every corner you may see warning, wiping and reset on ics can brick device, but its unfortunate you didn't notice it.
Anyway check your flash counter is zero and send it to service.centre to claim ur warranty.
If u running out of warranty, fing.a link for 'how to revice bricked note from my signature. And try it.
Edit : i wud like to know, as you said u went to cwm recovery, so at the time of wiping you wr on which kernel?
Sent from my GT-N7000 using xda premium

purple zebra said:
Hi all, I could really really use some help.
Today I decided to try and flash CM9 RC2 and I seem to have messed up big time.
I startred by rooting, using Dr Ketan's guide. That all went smoothly, and root was working.
I put the CM9 zip file on the SD card, turned off my phone, got back into CWM recovery, and most tutorials recommended, selected full data wipe... this is where something seemed to go wrong. While perfoming the data wipe, it seemed to freeze. I let it sit for a while, hoping it would sort itself out, but it didn't, and then it rebooted itself and went into a boot loop.
I can't get back into recovery mode, but I can get into download mode. So I thought the best thing to do would be to flash a stock firmware using odin.
I downloaded the latest german LRG firmware (which I was on before I started) from Sammobile, connected my phone to odin, selected the MD5 file, and pushed start. Again, this is where I got stuck. It just hangs on Nand write start. I've tried this twice now, and it gets stuck at the same stage (about 90% finished)
I have no idea what to do now and really need help. I'm not a total n00b, or at least I thought I wasn't, but I seem to have gotten in way over my head. What should I do?
Click to expand...
Click to collapse
Hi Bud,
From your predicament, first let me tell you what you have done wrong.... You mentioned you're in LRG Rom already and you wanted to flash CM9 after that.... right?
Well, I guess the process you did was totally wrong. You have to download stock GB N7000(from Dr. Ketan's thread) and using that stock GB Rom, that is the time you can install AbysNote kernel to root and install CWM on your phone. Now after that, download mobile ODIN (from google playstore) and flash the CM9 from there.
THAT's the one you should have done before. Remember, there are no easy way of jumping ROMS especially if your already in ICS... IF YOU WANT TO FLASH TO ANOTHER ICS ROM.
My rule of law would be to downgrade first to STOCK GB and from there, ROOT, install CWM and mobile ODIN and that'll be the time you can flash already to the new ICS ROM of your choice.
So here's what your going to do. Since your still able to boot in download mode, Download any stock GB ROM and flash it using PC ODIN. After that, seee if you can bootup your Note already to STOCK GB ROM. If and If you are able to already, then download a clean kernel preferably Abyss Kernel and flash it with your STOCK GB so that you can gain root and have CWM installed. From there, download Mobile Odin pro and flash the CM9 (that you ultimately want to be installed on your Note)
Hope everything's going to be fine and Good luck bud! :fingers-crossed:
Cheers!

Hello, I know its been several days, but I just wanted to update on the situation.
Thank you SO much to Dr.Ketan for pointing me in the right direction. A combination of these 2 guides (http://forum.xda-developers.com/showthread.php?t=1661590&page=2 http://forum.xda-developers.com/showthread.php?t=1667886) has managed to help me repartition my internal memory and get up and running again. I've got a stock gingerbread rom running, and all seems to be well.
I realise I was very stupid to do a wipe on an ICS kernal. I read about the problem for 1 particular Kernal back in may, and hadn't read the updates since, and so didn't realise it effected EVERY ICS kernal since then. It's my own stupid fault for not re-reading the warnings. Let this be a lesson kiddies, a little bit of knowledge is a dangerous thing.
Again, thank you so much for the help, to all involved, you are an asset to the community!

Phone won't boot

Hello, i have had my galaxy note for a couple of weeks now.
bit of this and that, you know how it is, flashing a few roms, checking things out, keeping it safe and stuff.
idiotic of me, didn't do a backup.
now
everything was working perfectly fine.
'till i decided to put some music on my sdcard
so i shut the phone down, open it up, take out the battery, take the sdcard, put it in pc, put some music (music i had on it before, so the files could've somehow magically ****ed up the device) then but it back on.
ever since, my device won't boot, it will go to CWM recovery, it will go to download mode, but not like, properly boot. all it does is show the Samsung Galaxy Note N7000 thingie, then screen goes black, and back again to Samsung Galaxy Note N7000, then black again, over and over again.
i figured, it must be something wrong with the bootanimation, had a custom one put there, so i deleted it, cuz that way it goes back to stock.
did that, didn't help, same thing.
then, decided to flash the rom again, even tho it was working perfectly for a few days now, (stock 4.0.4 deodexed zipaligned with hydracore safe kernel)
reflashed, didn't help, nothing happened.
things were weird, i thought i should go back to a GB rom, that always...fixes the problem.
tried to flash with ODIN, stuck at factoryfs, when i pulled the cable out, it would tell me the thingummyjig with firmware update has encountered an issue please bla bla kies.
then, I EVEN TRIED the kies, it won't connect, even tho my drivers are right, and i used kies with it before.
NOW, i thought to myself, ****, the phone won't go to recovery anymore, won't boot normaly, just in download, well, download a speedmod kernel which is safe and flash it, that should give you a CWM and safe kernel to flash from
did that, worked.
flashed the stock 4.0.4 rom again, then flashed philz latest kernel for the rom, and i'm back to square one.
nothing changed, i still can't use my note.
WHAT. DO?

right, well, i tried flashing alliance rom, and it gets stuck at mounting partitions....
the blue bar goes on and on till it gets out of the designated loading space
i can't wipe cache, i can't wipe dalvik, it just gets stuck.

Etnoscope said:
... tried to flash with ODIN, stuck at factoryfs ...
Click to expand...
Click to collapse
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.

ThaiDai said:
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
Click to expand...
Click to collapse
Thing is, phone worked flawlessly before, safe kernel,could flash anything,then this just happened....
Phone doesnt have warranty, sending it to some service would only have me end up with extra costs for putting the motherboard there, which i can do myself

right, welll
i tried flashing speedmod kernel with odin, it worked.
then i tried installing a GB rom via CWM
works well till it gets stuck at flashing modem.
what does this mean?

Etnoscope said:
...what does this mean?
Click to expand...
Click to collapse
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.

ThaiDai said:
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
Click to expand...
Click to collapse
tried flashing a stock gb with odin (tried 1 file in pda before, now i tried with 3 files(modem, rom, csc), same thing happened.)
stuck at factoryfs again
i didn't want to get to the partition scanner yet, wanted to clear out any other possibility first, using the scanner as a last resort.
what about pit files?
***
also, i really wanna thank you for showing some interest in my issue, means a lot to me, just wanted to let you know i really appreciate it, and i acknowledge the fact that you're a good, helping member.
thanks bro, you're awesome.

If you have tried also with the correct original pit, then it's time for the scanners to do its job

nokiamodeln91 said:
If you have tried also with the correct original pit, then it's time for the scanners to do its job
Click to expand...
Click to collapse
right
so, i've checked out this thread, about the pit method, and after i opened the emmc_find_brick_start.zip, it started scanning normally, and it finished without being stuck anywhere, and then at the end it said scanned 15027 MiB = 15757 MB completed --> OK then the ---end thingie and done.
so the brick start isn't there, which i assume means my phone is NOT bricked, at least not by the emmc thingummyjig
but if so, what the hell am i to do? like really?
tried flashing gb with cwm, stuck at flashing modem
tried flashing gb with odin, stuck at factoryfs
what the ****?

Get the pit file from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
Then flash the GB rom using pc odin. Make sure pit is selected and the repartition is ticked.
Also if you still have access to cwm try to install a CM10 rom first before trying out the above method.

SOOOOO
bit of an update.
right, after the whole emmc scanning brick mbs and stuff, decided to try and flash allianceROM 4.0.4 final
did it, worked, the flashing.
now i'm stuck at a non blinking, non changing non nothing, Smasung Galaxy Note GT-N7000 screen, with the yello jello triangle, same as before, but its not blinking now.

Ok. Try booting into recovery and performing a full wipe.

nokiamodeln91 said:
Ok. Try booting into recovery and performing a full wipe.
Click to expand...
Click to collapse
full wipe means:
factory reset
wipe cache
wipe dalvik
reboot.
right?
did that, as soon as i hit reboot, it got stuck again there, the frozen CWM screen.
battery in/out, back to square 1

Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey

nokiamodeln91 said:
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
Click to expand...
Click to collapse
official 4.2.1 will do?

Yeah

nokiamodeln91 said:
Yeah
Click to expand...
Click to collapse
any way we could talk via IM?
would be much better conversation-wise

We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe

nokiamodeln91 said:
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
Click to expand...
Click to collapse
i get status 7 error when i try to flash a CM rom btw, i know what to do, updating philz kernel as we speak
i want you to know i really appreciate this bro, couldn't have come so far without you. thanks a lot man.

right, well, i was using kangbang kernel, tried to install the cm rom, and it gets stuck at installing update...
been there for too long now,so i guess thats a safe bet.
gonna try with a different cm rom
right, well, apparently anything i try to flash gets stuck at installing update....
any solutions?

[Q] stuck in broken recovery mode

Hi everyone
First of all a little history:I used this [PhilZ-cwm6][n7000] v4.93.6 Safe Stock Kernel+CWM6+Root+exFAT+ext4-LT4 to root my n7000 on 4.0.4 (I bought it with 4.0.4).
Then after some time Android wanted an upgrade to 4.1.2 and after some time I just tried it and it failed after booting into recovery mode, because it didnt find a the expected kernel, I think. But I had the chance to boot up again.
OK I then did the update with Kies-Software and everything worked again. Then I rooted the phone again using the same method as mentioned in the post above.
Now today the phone wanted to update again, I thought, OK, if it didnt fail completely the first time, it will fail in recovery mode and let me boot up again.
But...
This time it went into recovery mode and didnt let me boot up again. It just shows the robot with the crystal and the progress bar seems to move a little but then the screen goes black for a second and the robot returns and the progress bar moves a little and the same again.... I dont get into the recovery menu.
I tried samsung kies emergency recovery, it doesnt find my n7000.
I tried to flash the kernel with a newer version from the post above. (I am not allowed to post there). No change it gets stuck in broken recovery mode.
I can push volumedown power and home to get into the download mode.
My question is what can I do?
Is there any other chance to avoid a complete stock recovery (is that the right term/way)?
What do I have to flash and how?
I am a little worried about the brick issues and I dont know which version I have to flash to set it back completely...
Please help & thanks
drz

No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.

cr0wnest said:
No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.
Click to expand...
Click to collapse
Thanks a lot, crownest!
I sweated a bucket of blood and seat, because I couldnt wipe cache and data first, but it worked!!!
Everything looks like before!´the update!
Some more questions (sorry):
do you think I should wipe cache and data now?
Is a stock rom like the rom on internal usbcard only?
What about the update? Can I update safely now?
Thanks again for helping...
greetz
drz

Yup you should be able to wipe cache and dalvik with no issues now.
I believe all ROMs be it stock or custom installs to the NAND memory (Someone correct me if im wrong) and never on your internal/external SDcard
As for OTA updates via Kies, I dont see why not, but if the same issue does reoccur again then my suspicions would point to a possible NAND corruption on the device. Not sure if there is a fix for that, but its a risk you gotta take. Or you can always root the phone and flash custom ROMs as new builds get released, this way you'll never have to use OTA updates again.

[Q] Help me understand whats going on.

okay, first of all i will say that im sorry if what im writing is full on faulty language. enlgish isnt my best. aaaanuslut i got my brothers old gt n7000 with a broken touchpad and screen for free. i repaired that with 160€ and my brother said that the phone was rooted. i found out he had allso overclocked the device. But after a few restarts to the phone it just said something what i think was in spanish or something "bla bla bla dos sistema". After that came not your old samsung logo, but purple blueish circles just circling. Ant thats it, it would not start. So i read about bricked devices, and as much as i understood i had a soft brick. so i was looking aroun the forum for some easy fixes becasue im totally stranger to this kind of hacking. i finaly found this http://www.youtube.com/watch?v=F97qo1moAR4 and i downloaded custom jb N7000XXLSZ_N7000OPSLS6_N7000XXLSO_HOME.tar. it did work but again after i tried to restart the phone it was stuck.
So since i dont want any custom stuff i think to my self why not stock rom. so i found this http://forum.xda-developers.com/showthread.php?t=1424997. But since i dont like JB as much as ICS i will try ICS. Her is the question: i allready did the factory reset and cache wipe but this instruction says not to FROM ICS.
Warning :
Don't wipe anything from stock ICS recovery
Don't factory reset/Hard reset on stock ICS.
Don't flash any Wipe version of ICS ROM
Does that mean that i have allready gone wrong or does that mean that you have to have ICS on youre phone and then you cant do any of those things? its really confusing and i dont want to fk up my phone.

Did you make a wipe on stock ICS recovery?

zai89 said:
Did you make a wipe on stock ICS recovery?
Click to expand...
Click to collapse
My brother said that he had custom ice cream on it when i first made the wipe and tried jelly

orizont said:
My brother said that he had custom ice cream on it when i first made the wipe and tried jelly
Click to expand...
Click to collapse
can your phone boot to recovery mode now?

zai89 said:
can your phone boot to recovery mode now?
Click to expand...
Click to collapse
Yes i can

flash via recovery phils kernel, (a newer one) reboot in recovery and perform the wipe for new rom option.
That should clean your device good.
Then flash what you want. After that download an emmc check app and check. Shouldnt be needed, but its nice to check.
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
flash via recovery phils kernel, (a newer one) reboot in recovery and perform the wipe for new rom option.
That should clean your device good.
Then flash what you want. After that download an emmc check app and check. Shouldnt be needed, but its nice to check.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Allright, thankyou, since i am new to all this stuff i will try to locate a tutorial. i dont have any idea for instance, what is recovery phils kernel.

at own risk, here http://forum.xda-developers.com/showthread.php?t=1901191. Download zip, keep zipped and put on external sd. Reboot recovery and flash via install from sd option.
Since we are going to wipe latest version will do fine. However if you plan to reflash the original Samsung rom one that is same or likewise version is best to quickly root after flashing rom, so you can flash speedmod kernel (better battery life) after. Find in original dev thread of this forum.
Remember, via factory format on phills kernel recovery(reboot in recovery) you have the option to do a wipe for new rom.
Otherwise on Phills kernel recovery do factory, cache wipe. In advanced dalvik cache, in mounts all(warning take out external sd before so you dont wipe that)
Then your phone is clean, you shouldnt have to wipe efs anyway, so dont tick that option ever in pc odin when flashing rom with odin.
This is the cleanest way to get rid of All leftovers and generally the way to go before flashing any new rom. However risk of loosing photos and whatever you have not backed up. In general backing up is bad as old files/db/etc are put back (risk of unforeseen stuff happening) Check one of my 5 threads for what backups there are. Via my profile you find them
Enjoy!
Sent from my GT-N7000 using Tapatalk 2

Okay, im thankful for all this information, useful stuff, got the PhilZ-cwm6-XXLT6-XSA-5.06.1-signed.zip.

let us know how it went, ok?

OOOKAY! so i finaly did what baz77 described. and rooted with another phils kernel witch i chose after my downloaded rom. Did root it, and after powering down and waiting about 3-5 sec. i started it, and it worked, no more getting stuck on gt n7000 screen and so on. and i also downloaded emmc check app, but unfortunatley it said. Brick bug: YES. Insane Chip.

sorry for double post, how do i delete? all i can do is use edit/delete button but it only edits the post, how can i delte it?

You cant but thats ok.
all n7000 have the brickbug to my knowledge, the test should state if the bug has been triggered, if not then super, if it has, best to secure the broken emmc sectors. Tricky.
I think having it clean now should eliminate earlier issues Enjoy your n7000

Thank you, i will, lately my n7000 has been rebooting randomly, any fix or know issue why this occures?

orizont said:
Thank you, i will, lately my n7000 has been rebooting randomly, any fix or know issue why this occures?
Click to expand...
Click to collapse
not sure how that is happening. Maybe a logcat (logfiles) shows whats happening when it happens. Could be app. Maybe rom issue. Method of elimination counts here.
On safe kernel, try dalvik cache, cache wipes and fix permissions in recovery, reboot and check if reoccurs.
Otherwise, updated versions, clean install I would recommend.
You can check also before with that emmc app if there are bad sectors. I dont expect it but you never know

Okay, its been a long time since i did that stuff. And it worked allirght. i got my phone working and rooted. Great stuff here

Sorry for updating old topic. Since people who have helped me with my phone allready are familiar with my case. I was wisiting a friend of mine in england and after i returned home my phone is f**ked. Everything works okay, but when i turn on mobile data or wifi it instantly freezes. Takes about 15-20 sec. and then phone does an automatic restart which restarting gets into boot loop. I have to hold down bower button to reboot again. When it asks me for sim unlock code, i have to be quick when im inserting it because i need to turn off mobiledata/wifi as soon as ia get my phone running again, otherwise it will freeze and crash again. Can it be somekind of virus or something? Is it most likely that i have to again format and install philz kernel and all that stuff? Thanks in advance.

that would be the best way to start..IMO

I really dont have the time or opportunity to format and reflash, but i guess its really difficult, near imbossible to tell whats wrong with my samsung. Bust still, any other suggestions?