this is what happened:
1) rebooted into recovery
2) backup
3) flash an inverted app via zip file - sucessful
4) reboot
5) i didnt like the inverted app so was going to restore my earlier backup
6) rebooted into recovery
7) flashed the restore
8) device stuck at "Samsung Galaxy Note N7000", cant get into CWM/bootloader
i had to go into odin mode and flash a stock rom
Did you try a battery pull and restart two or three times?
In the past I've had it stuck at the welcome screen a few times. I always wait ten minutes cos sometimes it does take a ROM that long to load, but when the phone gets so hot I've done a battery pull and then restarted a few minutes later. After two or three goes I've been lucky to get the phone back with the ROM i had selected.
TempusFudgeIt said:
Did you try a battery pull and restart two or three times?
In the past I've had it stuck at the welcome screen a few times. I always wait ten minutes cos sometimes it does take a ROM that long to load, but when the phone gets so hot I've done a battery pull and then restarted a few minutes later. After two or three goes I've been lucky to get the phone back with the ROM i had selected.
Click to expand...
Click to collapse
i diid battery pull restarts like 10-15 times and i even went to lunch for half an hour between as well so it was rested and everything
nobody knows?
Try wiping data I had same thing restoring to stock and had boot loop wiped data and it cured it !
marra2 said:
Try wiping data I had same thing restoring to stock and had boot loop wiped data and it cured it !
Click to expand...
Click to collapse
i reckon it is a problem with "system" not data because i flashed an old stock rom and it booted fine
Is your ROM an ICS ROM?
If so then follow this thread to restore your backup
http://forum.xda-developers.com/showthread.php?t=1613691
hmm
It probably crashed because it has different kernel, rom, CWM etc.
Flash your original rom first(rom you want to restore), and then try restoring your back up.
matius44 said:
Is your ROM an ICS ROM?
If so then follow this thread to restore your backup
http://forum.xda-developers.com/showthread.php?t=1613691
Click to expand...
Click to collapse
dsan45 said:
It probably crashed because it has different kernel, rom, CWM etc.
Flash your original rom first(rom you want to restore), and then try restoring your back up.
Click to expand...
Click to collapse
I was restoring a stock GB rom, no custom rom, no ics
Related
i wiped to data settings then i flashed darchlegendr5-05.zip... it stayed on HTC for like 10 minutes. i pooled the battery and when i tried to reboot it, it stays on HTC forever... Anybody know whats wrong???????????????
Why'd you pull the battery... -_-
Try to reboot it into recovery mode and restore your nandroid backup that I hope you did.
phone off hold down home hit power leave home held down boot to rec. wipe data then davilk reflash it and reboot
When flashing a new ROM, especially after a wipe, it can take upwards of 15 minutes to boot your phone. Just turn it on and let it sit.
If that fails, just load your nandroid that I know you made before all of this and start over.
Either you weren't patient enough or something didn't flash right. Try booting back into recovery, wiping again and flashing again. If it still fails try flashing to a different rom.
i think its working thanks but i pulled the battery because it took like 10 min and it didnt get past the first loading screen
xxxk15 said:
i think its working thanks but i pulled the battery because it took like 10 min and it didnt get past the first loading screen
Click to expand...
Click to collapse
Anytime you flash a new ROM, the dalvik-cache has to rebuild on the first run. This process can take anywhere from 5-15 minutes.
Open ADB Logcat and make sure you see lines of code that look similar to this.
Code:
dalvikvm\BEGIN:/system/app/app.apk
dalvikvm\END:/system/app/app.apk (success)
If you see that, it's rebuilding the cache and it's fine.
hello
i had clean installed the JB rom xxlsa on my note
my battery died while i was playing a game so i put the phone on charging
now when i turned it on its not starting
what shud i do
i booted into recovery and tried to clear cache and dalvik cache also reinstalled the rom from memorycard but still the same
can anyone guide me
Reinstall like the 1st time, do all wipes + formats then flash.
Is the phone looping ? Meaning on the glowing samsung logo, It vibrates then restarts the animation over and over again ?
Also, how long has it been like this ? Have you left the phone to charge for around 30mins before trying to power on ?
Im certain its nothing serious as you can still get into recovery and its still attempting to boot, So maybe its ROM / Kernel related.
EDIT: I just noticed you said its stuck on the Galaxy Note screen, not the boot animation... Have you by any chance just flashed philz kernel ? I had this issue the other day and I could only get it to boot by doing a full reset
BUT....... If recovery is working, Make a nandroid backup, reset the phone, then restore the apps from the nandroid using titanium backup. That way you wont lose any apps that you have installed since your last backup.
azzledazzle said:
Is the phone looping ? Meaning on the glowing samsung logo, It vibrates then restarts the animation over and over again ?
Also, how long has it been like this ? Have you left the phone to charge for around 30mins before trying to power on ?
Im certain its nothing serious as you can still get into recovery and its still attempting to boot, So maybe its ROM / Kernel related.
EDIT: I just noticed you said its stuck on the Galaxy Note screen, not the boot animation... Have you by any chance just flashed philz kernel ? I had this issue the other day and I could only get it to boot by doing a full reset
BUT....... If recovery is working, Make a nandroid backup, reset the phone, then restore the apps from the nandroid using titanium backup. That way you wont lose any apps that you have installed since your last backup.
Click to expand...
Click to collapse
thnx for quick reply
it has just happened to me few min back
it is stuck on galaxy note screen and not bootlooping (i think)
yes the phone was on charging in switched off mode for about 45 min to 50 min
in taking nandroid backup will i loose my sms and contacts
thnx
sitanshu91 said:
thnx for quick reply
it has just happened to me few min back
it is stuck on galaxy note screen and not bootlooping (i think)
yes the phone was on charging in switched off mode for about 45 min to 50 min
in taking nandroid backup will i loose my sms and contacts
thnx
Click to expand...
Click to collapse
Well your contacts will be backed up with google but im pretty sure a nandroid will back them up too, including sms's
Titanium will only restore apps from a nandroid, if you want to restore other things, try this app
What is disturbing is this just happened to me as well. My battery also ran down while using an xxLSA based ROM and won't boot past the "Samsung Galaxy Note" logo. Fully charging my phone so I can do a reinstall.
edit: Just confirming that Factory Reset fixes the problem. All my data is backed up so I went for it.
blud7 said:
What is disturbing is this just happened to me as well. My battery also ran down while using an xxLSA based ROM and won't boot past the "Samsung Galaxy Note" logo. Fully charging my phone so I can do a reinstall.
edit: Just confirming that Factory Reset fixes the problem. All my data is backed up so I went for it.
Click to expand...
Click to collapse
yes factory reset solved the problem for me
but now back to 4.0.4
Just to make another confirmation: This happened to me running an lsa based rom also.
Same here. LSA based Rom. Happened 2nd time already. So annoying.
octra said:
Same here. LSA based Rom. Happened 2nd time already. So annoying.
Click to expand...
Click to collapse
Me too. I tried at least 4 times to get v5 installed. It works fine until I try to install any app such as Titanium. Then it gets stuck at the first Samsung .. screen on the next reboot.
It's really p****ng me off. There must be a hell of a bug in this ROM.
This is the result of hurry. Let the developer test the firmware first. Not everything is flashable let the devs make a sacrifice first then on his recommendation install the FW
Sent from my GT-N7000 using xda app-developers app
Hello, I have a problem with my Galaxy Note and I don't know what to do.
A few hours ago I tried to start the device as I usually do after I turn it off, but the device does not turn on and only stays stuck on this screen: "Samsung galaxy note n7000".
I'm running this Rom: "[ROM][4.1.2 JB]Ultimate N7000 XXLSC JellyBean 4.1.2 v5.1".
I have the ability to log into CWM by the combination of the known keys
I hope you guys can help me, thanks in advance.
(Note: The battery is charged and i also tried to remove it and put it back in.)
This problem happened to me before with the xxlsa leaked rom
Do a wipe from a safe kernel and flash the rom again
Try to boot into recovery and do a reboot recovery and then reboot.
Else you may do a backup and restore the same backup. It works most of the time. But a little time consuming.
Had same problem by loosing power. The device wont boot anymore. Fix per, reinstall without wipe did not work. Switch rom
i believe this problem comes to all jelly bean leak always Stuck on the first boot.
just got this problem again how i did it ?press power on Stuck on first boot next step straight away press 3 button go to recovery n hit reboot system n my phone bootup n back to normal.
terminator_5505 said:
This problem happened to me before with the xxlsa leaked rom
Do a wipe from a safe kernel and flash the rom again
Click to expand...
Click to collapse
How can i replace the kernel and reinstall the rom if I cannot see the device on my computer when it's connected?
nokiamodeln91 said:
Try to boot into recovery and do a reboot recovery and then reboot.
Else you may do a backup and restore the same backup. It works most of the time. But a little time consuming.
Click to expand...
Click to collapse
I've already tried both methods you have specified and none of them worked.
My attempt to make a Nandroid backup has failed and the CWM said something like "backup of /data failed".
alvinhaw said:
i believe this problem comes to all jelly bean leak always Stuck on the first boot.
just got this problem again how i did it ?press power on Stuck on first boot next step straight away press 3 button go to recovery n hit reboot system n my phone bootup n back to normal.
Click to expand...
Click to collapse
Hi, this is not the first time I try to boot the device after installing a new rom.
I'm with this rom for a few weeks now and the problem occurred only yesterday.
This is well known problem with xlsc rom. U have to wipe everything and to flash rom. There are some solutions with backup/restore but they didn't work for me.
So, complete WIPE, and than flash!!
Backup of data failed because of insufficient space. Make backup to internal if there is more space.
i have the same problem since i full wipe and flashed asylums 20130302 build. after doing a full wipe and clean install, i started downloading my regular apps from playstore and suddenly it turned off just like when you remove the battery.
i tried the following::
1. full wipe and installed the rom -- it boots up few minutes then shuts off and wont boot up without charger
2. restored from nandroid -- same as above
3. full wipe and installed previous builds -- same
4. full wipe + flashed latest build 20130303 + latest gaps for JB 4.2 -- same
5. check battery stat -- ok
whenever it shuts off, it wont turn back on unless without a charger. it just shuts off at random. this is the second day I'm experiencing it and its frustrating.
any help? thanks
edit:: btw it shuts off at boot animation
In the other thread where you asked this question too there are members who replaced their battery and solved it this way.
Maybe you should try this and replace the battery.
Good luck.
I got same issue and I'm for kill someone. Why these problems on a official rom?
Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter
I'm trying to restore a backup on my phone, and it's stalled at 27% for the last 30 minutes and wont move. Is there a way to reboot the recovery and try to wipe and reflash a ROM or something?
Apoplectic1 said:
I'm trying to restore a backup on my phone, and it's stalled at 27% for the last 30 minutes and wont move. Is there a way to reboot the recovery and try to wipe and reflash a ROM or something?
Click to expand...
Click to collapse
TWRP sometimes does that. It gets really hot too. What I do is just use the hardware keys and manually reboot into recovery. If I were you just wipe the whole phone and attempt to restore again. You shouldn't have any issues the second time around.
mikeprius said:
TWRP sometimes does that. It gets really hot too. What I do is just use the hardware keys and manually reboot into recovery. If I were you just wipe the whole phone and attempt to restore again. You shouldn't have any issues the second time around.
Click to expand...
Click to collapse
Wiping and then restoring didn't work, stalled in the same place. Wiping, reflashing the ROM and then restoring did for whatever reason.
Thanks for tip!