Database Develop

Bootlooping with all custom ROM's after 2.2.1 stock upgrade

Ok, I upgraded my Milestone to official APAC 2.2.1 ROM. Was using it for a while, got bored and decided to go a custom ROM. I had previously successfully flashed MIUI and CM7 ROMS back on Eclair. Did a nandroid with Androdiani OR 3.3 and flashed CM7. Bootloop at CM logo. Pulled battery, reboot back to OR and tried flashing MIUI (stable version). Boot loop again at MIUI logo. Turned off using power button. Tried HO!NO!. Bootloop at M logo. Reboot, wipe, flashed FroyoMod. Bootloop again at M logo. Reboot, full wipe, tried iceandfire 2.9. Bootloop again at M. Gave up. Reboot, restored nandroid and everything is fine again. No idea what I've screwed up. Any advice?
Thanks.

Try wiping caches (both) and data in open recovery, then restart custom rom. Most custom roms require data/cache wipes.

Tried that. Wiped dalvik, and factory-reset before rebooting after flashing the custom ROMs. None of it worked. Cracking my head on this one.

Try flashing the 2.2 VR from http://android.doshaska.net/rootable, re-rooting the phone and starting the custom ROM process over again.

skadude66 said:
Try flashing the 2.2 VR from http://android.doshaska.net/rootable, re-rooting the phone and starting the custom ROM process over again.
Click to expand...
Click to collapse
Thanks. Will give a shot when get home from work and see if this fixes things.

Ok, tried flashing the 2.2 SBF with RSDLite. Checked version, exactly the same as what's already on the device. Flashed anyway. Restart, bla... bla... boot into Androdiani OR. Flash CM7, bootloop... damn... Nandroid restore.

Oh no! I can't get into bootloader mode now. I tried the D-Pad Up + Power button and it just boots up. No bootloader. Help.

afadzil21 said:
Oh no! I can't get into bootloader mode now. I tried the D-Pad Up + Power button and it just boots up. No bootloader. Help.
Click to expand...
Click to collapse
That doesn't make any sense.. did you do power+dpad-up and not the reverse?
Sent from my Milestone using XDA Premium App

I think I did Dpad UP+ Power. Got it to bootloader mode this time. Updated RSDLite to 4.9 and it recognised the phone when I plugged it in. Reflashed CM7 RC13 and gapps. Rebooted and... CM7 booted and started up. Crashing randomly though. Trying MIUI next.

afadzil21 said:
I think I did Dpad UP+ Power. Got it to bootloader mode this time. Updated RSDLite to 4.9 and it recognised the phone when I plugged it in. Reflashed CM7 RC13 and gapps. Rebooted and... CM7 booted and started up. Crashing randomly though. Trying MIUI next.
Click to expand...
Click to collapse
Yes! After reflashing bootloader everything seems to work. MIUI crashed. FroyoMod running ok. Trying HO!NO! next.

CM7 based ROMs don't seem to work well except for iceandfire. HO!NO! and CM7 crash frequently. But at least I can flash now..
Sent from my GT-I9100 using Tapatalk

[Q] While Flashing Restart (after Checking state of BML/MTD)

I wanted to flash CyanogenMod 7.1 on my Samsung Galaxy S.
I flashed before a Froyo Bootloader (because I had Firmware 2.3.3) on it, copied the CM7.1 Rom on internal storage and tried to flash through Recovery.
While updating it shows me the install process till:
Checking state of BML/MTD
then it interruptes the install process and restarts the phone. But then it just shows me the Samsung logo and nothing happens (=freeze).
No chance to start the phone, altough I restart it several times.
Then I can flash again with Odin to the starting state again. The files for that I found here (german):
http://www.giga.de/smartphones/samsung-galaxy-s-i9000/tipps/samsung-galaxy-s-cyanogenmod-7-flashen/
EZodin
EZbase-CSC-XXJV1.tar.md5
EZbase-PDA-XWJS3.tar.md5
EZbase-PHONE-XXJVE.tar.md5
Ezbase.pit
How can I flash CM7.1 now..?

Sometimes the cm7 rom will need flashed twice....you should be able to flash from any gingerbread rom also as cm7 was updated a while back to allow this. Try again, and if the phone starts bootlooping-pull the battery, replace and get into recovery-then reflash rom.

Unfortunately i cant enter recovery after unsuccessful flash. I have to use odin and flash back to old froyo... then i tried to reflash again to cm7.1 but it was always the same.
Thx anyway for ur answer...!
Hmmmmm ;(
Gesendet von meinem HTC Desire mit Tapatalk

no ideas? it is urgent.. ;(

it's really strange. it happened to me and I solved like this:
I removed the battery
volume up key + power button + home button
in recovery,I wipe everything and reflash of the rom
If recovery doesn't work, you need to reflash a stock rom, and a kernel with root and CWM

puuhh, at least another one who had this issue...
ok i understood that if i cant flash to cm7.1 then i have to chosse another rom, maybe just a stock rom.
but can anybody recommend a custom rom which will work? it is just a file system problem here, isnt it?

Done it!
Trying to flash the stable Rom didnt work.
Then i tried the nightly (181) and it took a while then it restarted. but when it was starting for the first time i got a loop while booting.
but this time i could enter the recovery (after stable installation it wasnt possible anymore) and i could reflash it (nightly again). and this time it worked!!! yeah finally after over 8 hours of work....
i hope i could help somebody who has got same issues

Glad you got it -and cm9 is now an easy upgrade from the latest nightly

Boot Loop after flashing stock

I was recently using Stunner ICS but decided I wanted to go back to stock and start over. I downloaded the stock N7000XXKJ4_N7000OXXKJ4 firmware and installed it through odin. I did not receive any errors on the phone or on my PC. But now it seems like my phone is stuck in a boot loop. It just keeps showing the samsung boot animation over and over. I used the download jig to get into download mode and tried redoing the firmware twice already with no luck. One thing I did notice is that the jig is no longer resetting the binary counter. Does anyone have any other ideas or is my phone possibly bricked?

This is supposed to be in Q& A section... Anyways... Did you try wipe?
Sent from my GT-N7000 using xda premium

What worked for me having the same problem recently is go to Recovery mode (Volume up + home + power) and you'll see this funny kinda recovery, not at all CWM Do a data wipe/factory reset and then reboot.

Same thing happened with me yesterday, wipe in recovery fixed the problem

priyanv said:
This is supposed to be in Q& A section... Anyways... Did you try wipe?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I'm sorry. Mods please move to appropirate section.
Thank you guys. I was beginning to freak out. I was trying to do the recovery menu but couldn't get it to work. I thought the recovery menu was also hosed but I had the wrong buttons. All is good now! thank you so much!

First thing you need to do if you want to get back GB, flash abyss 3.9 redpill kernel.
After that flash GB rom.
So later you can flash whatever kernel you want
Sent from my GT-N7000 using xda premium

Hanging at Samsung logo; can't boot into recovery; am I bricked???
Hi guys...
I've been semi bricked for about 18 hours now. And it's starting to look like it's a full-brick.
I had the latest Gingerbread ROCKET ROM on my Samsung Galaxy Note GT-N7000, with the latest Franco kernel in place.
I thought I'd give the ICS version of ROCKET ROM a go. Flashed Abyss4.2 kernel without any hassles. Used 'advanced' to boot into recovery. Did my various wipes. Flashed the ICS Rocket Rom zip. And got caught up in the recurring boot-up, mostly upgrade, run, reboot cycle that's been described in many places.
Didn't panic.
Booted into recovery again, and flashed the ICS Rocket Rom again.
But this time, it wouldn't go past the SAMSUNG logo.
Still, I could boot into recovery.
Which I did.
And I tried to restore my Gingerbread build from Nandroid.
Tried it. But it hung on the Samsung logo again.
With one key difference... Now, no matter how much I try, I can't boot into recovery.
I *CAN* boot into 'download' mode. So I've used PC Odin to try and inject a rooted Gingerbread rom into the phone.
The instructions tell me to wait for the phone to reboot twice. Sadly, it tries its first reboot, and doesn't get past the Samsung logo. And that's where it hangs. No recovery mode either.
What shall I do??? Oh, woe is me. Etcetera.
--------------------------------------------------------
UPDATE
--------------------------------------------------------
I found a version of Abyss 4.2 kernel in tar format. I flashed it via PC ODIN, and I now seem to have a phone that can boot again.
Not much more to report at the moment, cos the battery is on about 3%, so I'm charging it now before delving further. Will give more feedback once the battery's up and running again.
Here's a link to the Abyss file: http://forum.xda-developers.com/attachment.php?attachmentid=1072122&d=1337500067

I tried all of this, was on stock ICS 4.0.3 and had it rooted.
I tried to restore a backup which was sadly on GB and then the restore of /data failed
I then tried to flash paranoid custom rom and it was successful but the phone never went any further than SAMSUNG GALAXY NOTE GT-N7000 logo
I then Flashed a direct rootable stock rom via PC odin and all was well but the phone would never go any further than the logo before mentioned
I tried flashing AbyssNote kernel via pc odin but the CWM recovery menu kept on rebooting hence leaving me with not particular choice to select
Tried wiping data, cache mem, dalvik cache but no use and now i am on stock recovery menu. please help me out

i have this Samsung i9220 china i try to flash upgrade the firmware with Odin3 v1.85 . i got stock phone can't power non recover modem non booting logo , does anyone have any ideas ?

Can't install cm9

Hi,
I was running cm9 successfully for about 2 months, I would get occasions where the screen would go black and unresponsive. I had to pull the battery and reboot and it would be fine. I thought this was fairly normal for a cm9 nightly as it didn't happen very often. A few days ago this happened to me, and upon pulling the battery and rebooting, the phone just went into bootloops. I could not access cwm, so had to flash JW5 via odin, rooted it and attempted to flash cm9 again, this too results in bootloops.
Can anybody help? Being stuck with Samsung firmware is such a regression after having used cm9.
I've tried the same 2.3.6 firmware i installed with an older cm9 nightly which i know worked when i flashed it but get the same results.
Help me please.
Rob.

If you lose recovery you can usually get it back by flashing the semaphore kernel .tar in Odin

First Download and flash cm7 (Download From their official site). Thema cm9 : 100% works 4 me. Or look in The nighty thread and read The instructions
Gesendet von meinem GT-I9000 mit Tapatalk 2

slaphead20 said:
If you lose recovery you can usually get it back by flashing the semaphore kernel .tar in Odin
Click to expand...
Click to collapse
lol wish I knew that before, must have flashed Samsung 2.3.6 fully a good 10 times. Got it working now though, had to flash cm9 3 times in total; first time it flashes really quick and reboots into cwm with errors, then i had to flash it again twice and it installed properly. (I was only flashing it again once after the initial error).

I had this problem too. First, you don't need to remove battery, holding the Power-button will restart your phone even if it hangs. I never got the data back after the boot-loops. I recommend using titanium backup, I have it set to backup all my data every second night, so I can keep almost all my application data even if the nightly was bad.

Phone not booting after update

Hi, yesterday i update cm12.1 to 0918 build but i facing freezes and heating issues (the system hangs and i had to force reboot), tried to install tangerine kernel to change governors but no effects.
So i decide to reinstall a previuos build, i uninstall t-kernel and return to twrp_v6. But when reboot to recovery i have bootloop and cant enter to recovery, so i flash back the fota kernel to have back the cm recovery.
Now i cant even boot the phone, when press the power button i see a blinking green light and then nothing.
Should i try to flash back sony stock rom (4.3)? or a way to recover the boot partition? and if starting from 4.3 i can flash 5.1 or pass by 4.4 (i remember the first build of lollipop requires a 4.4 rom to install)
EDIT: i found tangerine 6.6 and fastboot, the phone boots, but after the kernel logo stop loading. if trying to go to recovery i have bootloop on twrp logo. now i cant shut down the phone.

mrjazzit said:
Hi, yesterday i update cm12.1 to 0918 build but i facing freezes and heating issues (the system hangs and i had to force reboot), tried to install tangerine kernel to change governors but no effects.
So i decide to reinstall a previuos build, i uninstall t-kernel and return to twrp_v6. But when reboot to recovery i have bootloop and cant enter to recovery, so i flash back the fota kernel to have back the cm recovery.
Now i cant even boot the phone, when press the power button i see a blinking green light and then nothing.
Should i try to flash back sony stock rom (4.3)? or a way to recover the boot partition? and if starting from 4.3 i can flash 5.1 or pass by 4.4 (i remember the first build of lollipop requires a 4.4 rom to install)
EDIT: i found tangerine 6.6 and fastboot, the phone boots, but after the kernel logo stop loading. if trying to go to recovery i have bootloop on twrp logo. now i cant shut down the phone.
Click to expand...
Click to collapse
Shutdown your phone by using the yellow button on the back.
If you want to recover the boot partition, I'd suggest you to flash stock fotakernel and boot.img of your ROM using flashtool.
Open your ROM zip with winrar and extract the boot.img from there.

the yellow button only reboots the device but after some bootloops shutdown itself. reflashing fota and boot not working, so i finally managed to reflash stock 4.3 with flashtool. thanx anyway
EDIT: i think (but not sure and no proof) the issue was caused by latest twrp recovery

mrjazzit said:
the yellow button only reboots the device but after some bootloops shutdown itself. reflashing fota and boot not working, so i finally managed to reflash stock 4.3 with flashtool. thanx anyway
Click to expand...
Click to collapse
you need to hold down the button for like 10+ seconds,
once it vibrates 3 times, stop holding it.
The phone will shut down.
Glad your prob was solved.
Welcome

mrjazzit said:
the yellow button only reboots the device but after some bootloops shutdown itself. reflashing fota and boot not working, so i finally managed to reflash stock 4.3 with flashtool. thanx anyway
Click to expand...
Click to collapse
Can you tell me which firmware you flash please ?

nathan30 said:
Can you tell me which firmware you flash please ?
Click to expand...
Click to collapse
the stock 4.3, i saved the file for my country times ago, if needed you can found a generic ftf somewhere on xda.