[Q] - Phone booting only in recovery - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hello,
I was using the Classic ROM v5 and decided to give the v6 a try. I didn't really like it, so I decided to get back to v5, that's when my problems started.
I did everything as usual, wipe data/cache/dalvik and flash rom, the problem is after I flashed the rom my phone it automatically reboots in recovery mod. I tried almost everything, I flashed the rom via Odin, I flashed a new kernel, I tried flashing via CWM (it gets stuck in installation). I don't really know what else to do
Some1?

Try flashing a stock Samsung Gingerbread rom like the N7000XXLC1. If it boots, do a full wipe in recovery. Then you have a clean slate to work with.

ginopunsalan said:
Try flashing a stock Samsung Gingerbread rom like the N7000XXLC1. If it boots, do a full wipe in recovery. Then you have a clean slate to work with.
Click to expand...
Click to collapse
Ok, I feel like a retarded now LOL I tried flashing a stock ICS rom and it didn't work, didn't even think about the GB one. Thanks.

Unless you have a safe custom ICS kernel, you are risking bricking your Note with a full wipe. Without a custom, always wipe from GB. You are still booting into recovery so I you have not bricked the phone.

ginopunsalan said:
Unless you have a safe custom ICS kernel, you are risking bricking your Note with a full wipe. Without a custom, always wipe from GB. You are still booting into recovery so I you have not bricked the phone.
Click to expand...
Click to collapse
Yeah, I got that part covered (few months ago I bricked my phone, had to replace the board. I don't really know what happened, it just kept booting on recovery, but I got that fixed
Thanks.

Related

[Q] Can't install anything through recovery

Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
+1 get clockwork recovery...you need to make sure the rom you are flashing is compatible with the version of CWR you are using.
For example a rom that needs to be installed with CWR3 you will need to install the zip presumably from CWR2. Pull the battery and reboot back to recovery - you should now be in the updated version of CWR. Then for safety sake - re install your zip.
Reboot and you should be all set.
I had lots of trouble going from 2.2 to 2.3. Flashing between 2.3 roms is very easy comparatively
milkytron said:
Hey guys, so I had MIUI since it came out and kept updating it every friday like I'm sure everyone else does that has it, but today I wanted to try out a Gingerbread ROM other than MIUI or CM7 so I went and tried to install Mosaic IV. I followed the tutorial on MobileTechVideos for installing it and when I got to the part where I had to install the zip from the sd card I did it and it got stuck at formatting partitions. So I waited a while, about ten minutes, then took out the battery and tried starting over from stock again. Then I realized that I was supposed to use a different kernel for Mosaic IV then the one Josh used in the video. So I downloaded that kernel and used that one instead of the one he used in the tutorial. And I couldn't get into recovery mode with it. So I flashed to stock again and redid the whole thing, this time I got into recovery and flashed it but it still got stuck at formatting partitions. So at this point I was like crap I have to get a different ROM. So I tried flashing Serendipity and that wouldn't install either. Then I tried MIUI again to at least get back to what I had earlier today, and I got an error while flashing the captivate-efsbackup zip in recovery. I have no idea what to do, all I want is to just get off of the stock firmware which im stuck with for now since I have to go to work in a little bit. If anyone can help it would be greatly appreciated. Thanks in advance
Click to expand...
Click to collapse
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
pwnerman said:
so your saying that you went to a gingerbread rom straight from MIUI? if that's true it failed because you didn't have the gingerbread bootloaders before you installed the rom
Sent from my Captivate
Click to expand...
Click to collapse
I did have the bootloaders, I went back to stock before I did anything just to be safe. I'm gonna try what the other guys said though right now, wish me luck haha
jmtheiss said:
I had a similar problem, and the ultimate fix for me was this:
Flash back to eclair stock (which you did)
Master Clear (aka format internal sd - make sure to back up your stuff first!)
Install CWM (may have to go manually - renaming to update.zip and reinstalling packages)
Wipe dalvik cache and cache partition, as well as user data
Install a stable Froyo ROM (take your pick, preferably a full-wipe with no bootloaders)
Reboot to CWM and do a second dalvik/cache/user data cleaning
(If you're going GB)
reboot to download mode
flash stock GB (WATCH OUT FOR BOOTLOADERS!)
boot it up, let it settle, reboot to CWM
flash your GB rom.
(If not)
Go where you would go from a stable Froyo Rom.
That's how I got back from a messed up phone with GB bootloaders to a working Mosaic installation. I can't say it will definitely work for you, but it may give you some ideas.
Click to expand...
Click to collapse
Alright so I have Andromeda 2.1 which is a froyo rom. Which method should I use to get to stock GB?
use Odin to flash gingerbread bootloaders then flash gingerbread roms
howtomen said:
use Odin to flash gingerbread bootloaders then flash gingerbread roms
Click to expand...
Click to collapse
I flashed the gingerbread stock rom and have it rooted with xcal's kernel, but when i flashed mosaic IV it got stuck at formatting partitions and i pulled the battery after about 15 minutes and then restarted my phone to find it stuck in a bootloop. So i had to start from stock again and now im back to gingerbread stock with root. I'm kinda scared to try again because it takes me like 30 minutes to get back to gingerbread stock with root. I think ill just stick with stock for a little bit

HELP Needed With Broken Phone

I've been flashing custom roms for quite a while but yesterday I got into some trouble and the situation that I have now is this.
I've installed a stock rom using Odin. The flash seems to go ok but when the phone boots it gets to the screen where you touch the green android to continue then a lot of force close messages come up.
I've tried flashing the stock rom with Odin a couple of times but I end up with the same result. Is there anything else I can try besides taking the phone to the repair shop?
Any help is appreciated.
If u flashing a GB stock rom, then i got the same backing from ISC LPY.
So i start phone in stock recovery mode (hold: up volume+power+home buttons) and do a full wipe. After reebot it was all ok. Just remember WIPE OLNY IF U FLASH GB ROM!!!!! Wiping in ICS may causes superbrick. Hope i help
appro77 said:
I've been flashing custom roms for quite a while but yesterday I got into some trouble and the situation that I have now is this.
I've installed a stock rom using Odin. The flash seems to go ok but when the phone boots it gets to the screen where you touch the green android to continue then a lot of force close messages come up.
I've tried flashing the stock rom with Odin a couple of times but I end up with the same result. Is there anything else I can try besides taking the phone to the repair shop?
Any help is appreciated.
Click to expand...
Click to collapse
If a factory wipe/reset does not work. You could try the following steps:
Put AbyssNotekernel42 zif file in your micro sd. Flash Abyss then boot into recovery of Abyss and flash the rom again.
tknguyencsu said:
If a factory wipe/reset does not work. You could try the following steps:
Put AbyssNotekernel42 zif file in your micro sd. Flash Abyss then boot into recovery of Abyss and flash the rom again.
Click to expand...
Click to collapse
This cannot be done from stock recovery.

Phone restarting after flashing to Stock GB ROM

Apologies, but since I am a new user, I was not allowed to post in the thread in developer section.
I had bought a pre owned phone, on Rocket ROM (GB based), however as S-Pen apps were not working I decided to go on the stock ICS rooted way.
I followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=1424997
I had downloaded the stock INdian ROM
N7000XXKK3 ------ 2.3.5 2011 November------ N7000ODDKK1 ------------------------India -------------------------Download
Click to expand...
Click to collapse
I followed the steps, downloaded Odin, and put the TAR file in PDA section, and flashed. All goes fine without error, on the phone it says everything is installed successfully. However after the process the phone just keeps restarting after the Samsung logo.
Have I done anything wrong here? How do I rectify the mistake and get my phone working
Did you clear cache/dalvik or do a wipe in recovery menu ? Looks like it's stuck because of leftover data from previous rom
Akiainavas said:
Did you clear cache/dalvik or do a wipe in recovery menu ? Looks like it's stuck because of leftover data from previous rom
Click to expand...
Click to collapse
Umm, pardon my ignorance as I am migrating from an ancient Nokia device.
No, I had done no such thing, no backups too as I just had it for a few days and no data so to speak of.
Should I be doing a wipe in recovery menu? And doesn't flashing the device, formats the memory too?
I think it should, but for some reasons it does not. To get rid of boot loop, go into recovery and clear cache. Should boot properly then
Also, avoid doing a factory reset on stock ics. If clearing cache wont help, i'd suggest flashing gb stock rom, doing a wipe and then upgrading to ics as wiping under ics has caused people a lot of troubles.
Yes you should do a wipe of cache memory and dalvik cache. That is availible from recovery menu. And no they arent allways formatted when flashing a new rom.
To go into recovery, do this.
Device off > vol-up+home+power. And now you are in recovery mode.
Also, avoid doing a factory reset on stock ics. If clearing cache wont help, i'd suggest flashing gb stock rom, doing a wipe and then upgrading to ics as wiping under ics has caused people a lot of troubles.
Click to expand...
Click to collapse
Thanks, I had read up how much ever I could, and am pretty wary of the emmc bug. Thats the reason I am flashing to a GB based stock rom, and then the ICS stock rom.
The error I got earlier is by flashing to a Indian GB Stock ROM, should I yet clear cache memory in the recovery mode?
A little bit of googling tells me I should be flashing to a ROM with multiple files (different ones for PDA, Modem, CSC etc) hence I am also downloading the stock Europe based ROM. Now the query is would the stock Europe GB ROM, cause any issues to a Note bought in India?
Edit: I wiped the cache partition in recovery mode, but the bootloop persists. I will try flashing to the Europe GB ROM and update.
Thanks, folks was able to install the Europe stock GB ROM, which I later flashed to an Indian stock ICS ROM. I have rooted the phone by a very helpful guide by Dr Ketan, however I miss some of the functions available to me on the rocket GB based ROM. Especially an option to have a data on/off option in quick notifications.
What is the purpose of rooting the stock ROM? Can I delete the bloatware that comes pre-installed on the stock ROM, once the phone is rooted? If yes how?
Any safe custom ICS ROM's you guys recommend? If I am right the correct way right now seems to be to flash a safe GB based ROM everytime before you flash an ICS ROM? Correct?
Last but not the least, thanks to the folks who replied and guided me in the thread, XDA is a very resourceful place, if you search it thoroughly.
About notification toggles - they are available in some roms, in others - not.
As far as rooting is concerned - yes, you can delete almost all the bloatware. There is a thread with APKs that are safe to remove - check it out and feel free to delete everything you won't be using. How ? Simple file explorer with root capabilities will do. Here's the list, thanks to pulser_g2:
https://spreadsheets.google.com/spr...1gdDJRekl4QmkyNmIzUmRvX2h3UDVkQXc&output=html
Safe custom ICS ROMs - I'd say go for CM9. For me, AOSP is the only way to go with Android. If you want TouchWiz based roms, however, can't really help cause i've never used them - there are plenty in development section though.
Nope, you don't need to flash GB ROM everytime. The problem with wipe affects only stock ICS roms ( so with stock-kernel based roms from Samsung, yeah, that's recommended ). But if you're going to flash/change/update roms like CM9, Criskelo etc. there is no need to go back to GB everytime.
Hi i was on ICS stunner and flash via PC Odin Stock GB rom.
everything goes ok but now i'm stuck on Samsung logo (bootloop)
i have to do cache/dalvik wip but i have only stock recovery.
Is there any way to do that on stock recovery or i have to flash a CWM instead ?
And if i have to so how to do that ?
help guys
arturutrata91 said:
Hi i was on ICS stunner and flash via PC Odin Stock GB rom.
everything goes ok but now i'm stuck on Samsung logo (bootloop)
i have to do cache/dalvik wip but i have only stock recovery.
Is there any way to do that on stock recovery or i have to flash a CWM instead ?
And if i have to so how to do that ?
help guys
Click to expand...
Click to collapse
Download abyss from the following site:
http://downloadandroidrom.com/file/...rnel/AbyssNotekernel42CWTouchOriginalLogo.tar
Flash the file with PC odin then reboot into abyss recovery. You can then do the wipe.
If you need more information, go to this website:
http://rootgalaxynote.com/galaxy-note-root/how-to-root-galaxy-note-gt-n7000-method-2odinheimdall/

[Q] abnormal error, can anyone help me?

Hi,
I as of yet, am not going close to any ICS build till the issue gets solved by someone.
so I am experimenting with different gb roms. i was using checkrom v6 but didnt like it, so followed steps to install darkyrom/alliancerom extreme edition. i followed the steps as I was told to install allianceota and flash the rom through there. it didnt work. so instead using cmw i flashed through recovery, it did flash but there no root.
so now, i reflashed a stock la6 rooted rom from here; http://forum.xda-developers.com/showthread.php?t=1535025
this went smoothly with no problems, so i installed allianceota as normal, this time when i try to flash the following messages come up:
Installing Multi-CSC
Can't access to '/system/CSC/KOR/system/'
Successfully applied multi CSC"
and then it gives me the option to reboot, wipe cache and a few other options, not full recovery mode.
shall i just reflash the rom through recovery, or am I doing something wrong? and does the slight error above mean I have a problem with my note?
cheers in advance.
Let me just say that almost every ICS ROM out there now has disabled the MMC_CAP_ERASE code in the kernel that activates the eMMc bug and bricks your phone. If you want stock ICS, you can use SpeedMod or Franco kernels. If you want AOKP, there is that now. If you want CM9, there's a bunch of variations plus the official CM9 nightly. If you read through the OP and stickies, you will be okay.
Are you on stock recovery still? It sounds like it from the error you are getting. Try flashing CWM recovery and installing the GB rom with that. Follow Drketan's thread in Android Development.
hmmm, so would you advise me to use ics? is it much better? i dont want to use cm9 builds as i need the spen apps and so on. i have looked into kingdroid or alba.
I'll have to think hard about this. i may give it a shot soon though..
oh and btw, I fixed the problem, yep it was to do with cwm it wasn't installed with the stock rooted rom. as for allianceota, it still didnt flash the rom, i had to flash the rom through cwm manually.
cheers anyhow.
salespalace said:
hmmm, so would you advise me to use ics? is it much better? i dont want to use cm9 builds as i need the spen apps and so on. i have looked into kingdroid or alba.
I'll have to think hard about this. i may give it a shot soon though..
oh and btw, I fixed the problem, yep it was to do with cwm it wasn't installed with the stock rooted rom. as for allianceota, it still didnt flash the rom, i had to flash the rom through cwm manually.
cheers anyhow.
Click to expand...
Click to collapse
I love ICS a lot more than GB. If you want to use stock ICS, I would just use Franco or Speedmod kernels with it and be safe. Read both of their forums and decide what you want to do.
I had the same problem with rom deodex i had flash with odin 1.85 firmware gingerbread here ; http://www.hotfile.com/dl/152168378/f76281c/N7000XXLC1_N7000OXXLB3_ATO.zip.html... then i made wipe cache and cache dalvick .
I've just flashed AlBa repack latest one on xxlq2, I did it by following the steps,
I thought i had broken my phone, because when the flashing finished and i was rebooting, at the beginning when it welcome to galaxy note n7000 and then goes to the bootup video, it restarted that several times, then after like a few minutes it loaded the homescreen and startup.
salespalace said:
I've just flashed AlBa repack latest one on xxlq2, I did it by following the steps,
I thought i had broken my phone, because when the flashing finished and i was rebooting, at the beginning when it welcome to galaxy note n7000 and then goes to the bootup video, it restarted that several times, then after like a few minutes it loaded the homescreen and startup.
Click to expand...
Click to collapse
-Flash a stock GB rom with pc odin
-Root it
-Go to cwm and wipe all (factory reset,cache and dalvik and then Install the ics rom that you like
-Reboot system and now it should work
Sent from my GT-N7000 using Tapatalk 2

Stuck mith mu GNote

Hi,
I' in trouble with my note. It stucks at samsung logo animation and i cant make it boot to ics anymore (i'm on stock 4.03 ics rom)
This is what happend : i played/bench beetween gl_notecore kernel v9.x/v10.x and chainfire 3D driver install/uninstall, all was fine and suddenly my phone freezed at ics homescreen after a soft reboot (OC or whatever make it freezed).
So i hard reboot it by pressing power button 10 sec, and now, it dont full boot anymore.
I tried to flashed many kernel through cwm onboard kernel stuff (notecore/speedmod..), tried wipe cache, tried to flash stock rom (N7000XXLQ3_N7000XXLPT_N7000XEFLP1_HOME.tar.md5) throught odin but result is same. Phone is indefinitly show samsung animation logo screen without finally boot into ics.
I dont know if chainfire 3d driver is the guilty one but fresh rom flash dont unbrick it ?
What's my solution now ? i didnt tried to full wipe before flashing stock rom and i'd prefer not. but...
thanks for your help :good:
To be on safe side i would try to flash a stock gb rom first then move to ics later. Flash gb stock from dr.ketan thread then go into recovery and wipe ....then it should boot.
Sent from my phone
Thanks for reply.
So i'm going to download a gb stock rom and wipe it from there if necessary.
Shuff said:
Thanks for reply.
So i'm going to download a gb stock rom and wipe it from there if necessary.
Click to expand...
Click to collapse
Download a GB Rom from here http://forum.xda-developers.com/showthread.php?t=1424997
Flash it using PC Odin. If your phone stuck at bootscreen logo or you face any issues do a Wipe by going to recovery mode. (GB Kernels are safe to Wipe)
Now Check whether the issue is still there or not.
Gb flashed successfully, and phone boot normally.
But GB soft reboot a lot. Seems flashing gb over ics without a wipe make a mess in the rom =)
Going to wipe and flash ics back.
Tanks a lot !
Shuff said:
Gb flashed successfully, and phone boot normally.
But GB soft reboot a lot. Seems flashing gb over ics without a wipe make a mess in the rom =)
Going to wipe and flash ics back.
Tanks a lot !
Click to expand...
Click to collapse
Remember not to WIPE on ICS Stock Kernel. When you want to flash on Stock ICS remember to flash a safe kernel first like notecore/hardcore/etc
No matter, i'm aware of MMC_CAP_ERASE brick of the death
I will do like i did before. flashing notecore kernel through odin and triangle away
Edit : oh wait.. and i'll never install chainfire 3d again

Categories

Resources