Hi Everyone,
I have a GT-N7000 - it's been working great since I bought it 9 months ago. I was running RocketRom on it for months. I've been using RR 11 (I didn't like 12) and haven't had a problem with it. The CWM that comes with it appears to be 6.0.1.2 and I kept the stock kernel (OneNote??). Lately, my sms messages were being sent sporadically and I kept getting this same SMS pop-up over and over (every time I sent an SMS). I know it's probably a carrier issue but I thought I would boot into recovery and wipe the cache and Dalvik. I've done this several times in the past without problems.
I first wiped the cache, then I did Dalvik. For Dalvik, I got the error E:\ unavailable (I recall seeing this in the past). I select "Reboot" and the phone booted back into CWM. I've tried removing the battery and same thing.
I ended up trying to flash back to the pre-rooted GB using Odin. The flash completes and the phone reboots but, yep you guess it, CWM comes up. It's the same version. So apparently this is not being updated by Odin??? I read somewhere that this is a CW bug that does not clear a flag to boot back into Android but the fix seems overly complex and worries me (I'm not afraid of doing it if it will fix it).
I'm entertaining the idea of using Kies to do a "Firmware Upgrade" which looks like it will install the latest ICS. It successfully downloads the new firmware then asks me to connect the phone. Before I do this, I wanted to check here to see if this is my only (best) option. Or if I should try something else? Also, Kies says system and data will be initialized so will my sms logs, photos, etc be deleted as well? Not a huge issue since I save the photos to the external sd. I just want to know if the USB storage will be wiped too.
[EDIT] I wanted to add that I TRIED to install Abyss from CWM and it hangs. Same ting with installing RR again. It appears that the file system is locked or something. Pretty much nothing works in CWM. I even tried mounting the various partitions then installing Abyss. It just hangs on "installing." I suspect the problem occured when I wiped the cache or Dalvik. I just don't know what
I appreciate any input.
Thanks!
dont use abyss... try other like hydracore or speedmod 3-15
Im a noob and im afraid i may have this also..
Try to download Philz kernel for your built number, and flash the philz zip file from recovery.
or if can't flash from recovery, try to download the ODIN file for philz kernel (TAR file).
It should re-injected the CWM.
Sent from the corner of this rounded earth.
Related
First of all I hope this is in the right place: I did do a search but still couldn't find any help.
Here's my problem:
After getting a (delicious) taste for customisation after rooting and lagfixing, I decided to give custom ROMs a go. Hours of indecision passed and ultimately I settled on Doc and Stefunel's magical ROM. Due to currently being on 2.1, I chose to follow the set of instructions provided on the page for doing so.
All was well up until the very final step. When rebooting the phone through ClockworkMod Recovery, instead passing the Samsung boot screen into the Android system, the phone boots into CWM recovery. I've tried doing another factory reset, and reinstalling the ROM to no avail. I've also tried mounting "/mnt/sdcard" in order to place another ROM to flash from, but I keep getting a message telling me to insert a disk (what happens when you don't mount).
That's pretty much all there is to it. I'd be massively grateful for any help!
-anti
If you have made a backup of your apps then flash the JPY with Odin and then make factory reset in recovery mode. Then root with CF Root 1.3 (Or something like that) and flash CWM Recovery. That's what I would do.
Sent from my GT-I9000 using XDA App
from the recovery menu try wipe cache and dalvik, and reboot
Hi all,
So after I flash a new ROM (MIUI MGv2/RC8vC/MGv1) I always hang at the Galaxy S GT-I9000 screen - the first boot screen.
I am wondering what this means? is it a corrupt file, something wrong with my internal sdcard, ROM not installed properly?
Please help,
Thanks.
some times a wipe from recovery will help and goes back to normal boot
many issues may cause this problem for instance if framework.jar or android.policy.jar or... have some bugs , will happen like that
Hi,
By wipe you mean clearing the formatting system, data, cache, dalvik cache and a factory reset? I ask this because the MIUI roms are not are non-wipe and the instructions recommend you to format those places before install (which I did).
I mean wipe cache partition from recovery. just try it and ley us know if it works
Well I just tried again but it doesn't work because I can't access recovery mode. It hangs at the Galaxy S screen and doesn't move from there so I'm wondering why because if I can't fix the bad install then I can't access the recovery mode and can only flash.
if recovery dont work BUT download mode does,
start the whole process again, flash back to stock froyo with froyo bootloader.
did you come to MIUI from Gingerbread ??
Well i've done the process like 10 times, nearly every single time from froyo (JPU,JS5,Ezbase 2.0) and I also went from 2.1 to 2.2 and then to MIUI. The other times I have tried coming from CM7 as CM7 works.
well i have a similar issue but in my case i just wiped my data thru cwm on darky v8 xxjpy..
now i get boot loops,any idea what should i do??
i know this is not exactly the thread but if i get my answer it'll save me from starting a new one..
When I got bootloops i normally reflashed. If you don't have data it will probably work?
I assume you have data as your on Dark v8 when V9 is out?
i dont understand by have data??
i flashed v9.5 but went back to v 8 few months ago..
today i just wiped/factory reset my phone using cwm and it was succesful but now its bootloops and vibrations..
i never wiped my phone before and only have flashed using cwm,never used odin for flashing roms!!
OH I see, by data i meant personal data that you might want to back up...I'm not to most knowledgeable but I know how to flash roms. I reckon you should try to flash V8 it again if you can enter recovery.
This concerns my galaxy note n7000. I had a rooted checkrom v4 working on my note. I tried to install criskelorom v2 and got bootloops. I then tried to go back to stock via odin and flashed stock N7000 KL3 ROM which i had earlier used, I had to go to stock because after bootloop even recovery was not working. now after flashing stock i am getting a strange problem of the phone getting stuck at the welcome to gt-n7000 screen . "touch the android to begin" . nothing is happening after touching the android on the screen although i can change the language etc and even the pull down notification is also working but the phone is stuck at the initial stage. I have a nandroid backup of my initial checkrom in my internal sd card but cannot restore it before installing a rom with root and cwm. Kindly help . Thanks.
I'm having the exact problem. I'm hoping we can create a soft brick sticky thread. I walked away from my phone last night because I was getting frustrated.
My attempts to flash stock ROM via Odin resulted in the "not responding" message in windows. I can get to both CWM and download mode, however any ROM flashed via CWM results in the behavior described by the OP. fortunately I have access to another Samsung phone, so I can double check driver installation (although it worked for flashing previously).
I'm continuing a search through the forums to find some alternate methods for unbricking. Hope someone has an idea.
Thanks!
It seems that the stock roms i was trying to flash were nonwipe ones so i flashed xxla3 which is a wipe rom and was able to boot . I then flashed the earlier kl3 rom over this rom because kl3 is rootable. I then rooted and installed cwm booted into recovery and restored my earlier nandroid backup. I think the situation arises because the nonwipe rom was unable to clear the cache , user data etc
Thank you for the information. I had exactly the same problem. What did you use to root KL3 ?
Just wipe both cash and user data, and reboot.
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
and do a factory reset and wipe cache.
problem should be solved cause that's what i did
Flo1389 said:
Just wipe both cash and user data, and reboot.
Click to expand...
Click to collapse
Thanks
liewkingyan said:
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
And do a factory reset and wipe cache.
Problem should be solved cause that's what i did
Click to expand...
Click to collapse
daaamnnn!!! I'm scared to dead because of this!! Thanks dude!!!, no more **** ass ics
I had an issue like this once or twice.
http://www.youtube.com/watch?v=L5XjF6sPef4
This skips the that screen. then I cleared some things like google framework and it all was peachy
But its not wroking for me
Update: Solved
Thank you for everyone's reply and help.
What worked for me:
Downloaded Mobile ODIN v3.10
Downloaded Goku v1.5-10 TAR (Kernel-Goku-V1.5-10.tar)
Flashed firmware with Mobile Odin with MD5 signature check
Can now boot into recovery
Currently on:
CM9 Version 9-20120515-Nightly-n7000
Build date Tue May 15 23:06:26
Kernel version 3.0.30-CM-q6804ca8
I cant seem to get into recovery while using any of the ICS roms. I've tried several CM9 bulds, Kindgroid, Stunner and a few others. I doesn't matter if i try to access it through the hardware keys (press and hold the Volume UP+Home+Power) or through one of the software options (reboot into recovery). After the samsung logo apears the screen will turn black. I'll have to restart the phone with the power key.
Everything else seems to be fine. I can get into download mode just fine. I have no problems downgrading to a gingerbread rom from pc odin or mobile odin. Also theirs no problem for me getting into recovery from any of the gingerbread roms I've tried.
I first noticed this while I was on ICS stunner. It was the build with the affected kernel. Everything was running smooth for me. Recovery and everything else seemed to be working fine but when i started reading posts about the brick scare i became afraid of doing anything else on that kernel.
I followed Entropy512's advise:
If you are running an affected kernel:
STOP USING IT IMMEDIATELY. FLASH A SAFE KERNEL USING ODIN/HEIMDALL.
DO NOT wipe in recovery
DO NOT flash anything else in recovery
In general, DO NOT use recovery at all
I flashed his DAFUQ releas using mobile odin while still on stunner. Everything seemed to go smooth. After flashing I checked under setting -> about phone -> kernal version and his kernel was properly displayed. I tried going into recovery but the screen would turn black after the samsung logo.
I've must of done something wrong while flashing Entropy512's kernel because ever since I flashed his kernel I havent been able to get into recovery while running an ICS rom.
TL;DR
Cant access recovery from ICS roms but recovery works fine while on gingerbread roms
Did you try before flashing ics do a 3 wipes first while in girgerbread for a clean installation?
jonpaslim said:
Did you try before flashing ics do a 3 wipes first while in girgerbread for a clean installation?
Click to expand...
Click to collapse
Yeah it was one of the 1st things I tried when I encountered the problem.
Can anyone confirm if the recovery is stored in the same place for both ics and gingerbread? I feel like I might have damaged some sectors and might have some bad blocks. Everything else seems fine though.
runnin4mayor said:
Yeah it was one of the 1st things I tried when I encountered the problem.
Can anyone confirm if the recovery is stored in the same place for both ics and gingerbread? I feel like I might have damaged some sectors and might have some bad blocks. Everything else seems fine though.
Click to expand...
Click to collapse
How about 4 wipes including format/system and also use jbroid even though your not installing a kernel but rom still use it.
Flash stock GB rom. Reroot it and then check everything is working fine? If yes then flash ICS rom.
Sent from my GT-N7000 using XDA Premium App
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
runnin4mayor said:
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
Click to expand...
Click to collapse
In the system setting of the phone there is back up and reset and there you can format usb storage, this will format your internal sd, this is in ics setting i forgot about gingerbread. You can do this while in gingerbread to be safe, format your internal sd.
jonpaslim said:
In the system setting of the phone there is back up and reset and there you can format usb storage, this will format your internal sd, this is in ics setting i forgot about gingerbread. You can do this while in gingerbread to be safe, format your internal sd.
Click to expand...
Click to collapse
Yes.. I've tried that before installing my current ICS rom. Actually I formatted both the internal and external SD while still on GB. I'm still wondering if the recovery stored in the same partition space in both GB and ICS. I can't understand why I can access CWM recovery on GB but not while I'm on ICS.
i too have the same problem even though i can access cwm manually cant install any zip file but if i use abyssnote kernell everything works fine the problem started when switched over to ics from gb
runnin4mayor said:
Thanks for everyone's reply
I've tried jbroid and formatted system but it didnt help. Like I said... everything is fine on GB, recovery and everything else. I've been back and forth several times already. Everything seems to be working fine on ICS too. I just can't access recovery no matter what I do while on ICS. I'll try wiping 4 times from gingerbread this time.
Click to expand...
Click to collapse
Wiping more than once is pointless... I don't know where people get silly ideas like "wipe 3 times".
When you switched to something else, did you flash it using CWM or Odin?
Try flashing a different kernel using Odin. I have seen that in rare cases on some devices, doing something like the following:
Flash one kernel from a recovery
Reboot directly to recovery using CWM's Advanced menu
At this point, the device will be stuck either always booting to recovery or never booting to recovery
Flashing a kernel with Odin/Heimdall - NOT "Mobile Odin" (I hate that name because it's completely different from Odin) or CWM often breaks these loops.
problem accessing recovery
hi today i solved my problem of not unable to find cwm in programs and flashing zip files from recovery while on ics. first i flashed abyssnote kernell then rebooted into recovery did all the three wipes and in addition formatted data, system and cache. then used jbroid kernell cleaner. installed fusion rom flashed green theme rebooted at last could see cwm in programs can flash any zip file now
Thank you sir for your swift action.
deepalakshmidas said:
hi today i solved my problem of not unable to find cwm in programs and flashing zip files from recovery while on ics. first i flashed abyssnote kernell then rebooted into recovery did all the three wipes and in addition formatted data, system and cache. then used jbroid kernell cleaner. installed fusion rom flashed green theme rebooted at last could see cwm in programs can flash any zip file now
Click to expand...
Click to collapse
How did you flash abyssnote kernel without being able to enter recovery?
Edit: Solved my problem. Updated 1st post
Hi guys. I'm quite a noob, but have a good experience on flashing without be bricked (CM9, CM10, Crash, Paranoid...), but I have a problem.
I will explain to you step-by-step what I've done with my Note, so I wish some of you could help me.
1) I was running JB Crash ROM with PhilZ kernel.
2) Some apps got Force Close too often, so I went on Rom Manager and, after a look into the "Fix permissions" description ("It will fix some force closes" or something like that), I decided to give it a try and I tapped on it.
3) After that, my homescreen became unusable, because "TouchWiz Home" got EVERY TIME force closed without reason. Everything else worked fine, so I deciced to boot into CWM recovery to restore a nandroid backup of the same ROM.
4) Instead of tapping "restore", I tapped "backup" (my fault) and it started without possibility of get back. I got something like 200 Mb of free space, so in every case it will never have had success. My Note stucked at this point, so I decided to reboot manually (vol up+home+power) into recovery. Finally I tried to "restore" but I get this message: "ERROR WHILE RESTORING /SYSTEM".
5) I tried to reboot my Note, but it stucks at "Samsung Galaxy Note GT-N7000" screen without going on.
The good news is that it can go without problems into recovery and into download mode. What can I do? Flashing from CWM, for example, CM9 can fix this?
Please help me thanks!
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
friedje said:
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
Click to expand...
Click to collapse
After formatting /system, can I try to restore my nandroid backup? Or I have to necessary reflash my ROM? In that case, it's the same thing make it via CWM or via ODIN PC? I'm still on PhilZ recovery, which is safe I guess!
Anyway, thanks for your help
Via CWM or Odin, depends if you have your rom in the zip or the md5.tar format.
I would reflash to be clean. It's a bit more work in restoring your apps and data
afterwards, but at least you don't restore any messed up files.
if you can still access CMW and Download Mode then you probably are not brick... try fresh install through pc odin.. safe method no need to worry about bricking by fullwiping on unsafe kernel or raising triagle or binary counter whatsoever.. if you wanna play safe then PC ODIN and after that you can root your rom
Thank you guys, now I'm on stock ICS flashed via PC Odin and everything works fine I knew I was 99% not-bricked (still recovery and download mode avaiable), but I was a little scared too.
Thank you again!
glad you solved it.. :good: