So here's what happened on my note..
I was running the XXLRQ rom rooted with CF-root kernel and then this OTA update popped up on my phone 2days ago (approx 5MB).. Since I just woke up that time and I don't know what hit me (stupid me) I continued with the update even if I'm aware that running OTAs on a rooted phone can give you problems.. And boy I GAVE ME ONE HELL OF A PROBLEM!
When the phone rebooted, it just shows the "galaxy note GT-N7000" screen and totally blank after that..
1. Did battery pull after 5mins and attempt to boot to recovery - no respone, still black screen after the "galaxy note GT-N7000" screen.
2. Was able to boot to download mode and flashed stock prerooted gingerbread Dr. Ketan's thread and i know that file is working fine since its on my computer for 1month already and ive flashed that copy 100% fine - flashed ok via pc odin, rebooted but still same behavior.. cant get into recovery also to do a full wipe.
3. Flashed my XXLRQ rom copy on my computer - phone booted up fine with all my info in it then I got the SIM-Lock and no root (since the CFroot kernel was overwritten perhaps?)
4. Was able to root it and since I just want a clean phone again, tried reflashing the Prerooted Gingerbread again via Mobile ODIN v2.30 (this has never failed me ever since) but the problem reappeared! - cant get into recovery either..
5. So I was left with no choice but to flash that XXLRQ again via PC ODIN and root with PhilZ's stock kernel that i just found out 2days ago since its very new.. - EVERYTHING went fine with no glitches or hiccups and was able to wipe everything clean (data/cache/dalvik).
6. Tried flashing Prerooted Gingerbread again.. Mobile odin passed but problem reappeared.. Same case with PC odin..
7. Reflashed XXLRQ again from MOBILE ODIN this time and added PhilZ's kernel and everything went fine..
7. Ran the EMMC Brickbug Check to make sure my phone is still in pristine condition and it PASSED the test.
So here's my question:
1. Any ideas what happened there? what was that update from the XXLRQ rom?
2. Moving back to gingerbread using PC ODIN should wipe everything fresh when it comes to the aspect of bootloader/kernels but not the data which should be wiped clean by wiping from recovery right?? so why is the problem persistent..
Now I'm not confident enough to flash this phone again because it might have a problem lying deep inside that cant be fixed by wipes...
Anything
but most likely cache or dalvik cache/unclean update procedures. Either cf stuff or ics stuff could also conflicted.
Gb flash was probably nonwipe rom, so stuff from ics rom/cf kernel conflicting with gb stuff. A factory reset in gb, which is safe, ICS not, could have solved that. Update back to ics was probably a fluke, unless the conflicting stuff was overwritten with the ics rom/modified kernel.
Clean procedures safely executed are always best to prevent this. This includes original components unmoddified for otas and kies update ability.
Off topic tip: efs backup, cause that seriously go wrong with updating.
Sent from my GT-N7000 using Tapatalk 2
Recently there were some minor updates from LRQ streamlined to the phone itself (which has LRQs installed already), these minor revisions (some says) increased the performances of the phone itself.
1. Yes that small update was for the LRQ rom itself... minor updates I should say. The cause on why your phone almost got toasted was and is still unclear to me though. It could be perhaps your phone was never toasted.. You should have perhaps waited more than 5 minutes before.. I'm sure it would have booted up still. But I guess the fact of the matter is,, you panicked after that (after seeing the Note's Logo for 5 minutes only)... He'll I've seen and even experienced my phone to boot up (after flashing a custom rom) around 10 minutes tops... but I did not get fidgety or panicky about it... I guess you may have just push the panic button all too soon bud... You could have waited perhaps even like 8 mins to really verify if it already stucked on the boot logo thing...
2. Going back to Stock GB does not WIPE your phone clean.. you have to initiate really a manual wipe once your in stock GB.. WIPE data/partition, dalvik cache... that is to me the surefire way to wipe clean all the cluttered remnants of the previous ROM you've used before.
It was the Update of N7000XXLRT
nokiamodeln91 said:
It was the Update of N7000XXLRT
Click to expand...
Click to collapse
what makes you say it's the XXLRT when the OP explicitly said he has XXLRQ already on his phone, when an OTA update popup on his screen.
your post is kinda misleading and confusing...:
capitansid said:
So here's my question:
1. Any ideas what happened there? what was that update from the XXLRQ rom?
Click to expand...
Click to collapse
letters_to_cleo said:
what makes you say it's the XXLRT when the OP explicitly said he has XXLRQ already on his phone, when an OTA update popup on his screen.
your post is kinda misleading and confusing...:
Click to expand...
Click to collapse
Yes the OP was on LRQ and he got an OTA of 5MB which i meant was the update for LRT
Country/Carrier Date Final PDA Size
Germany 7 Sep 2012 N7000XXLRT 5.7 MB
baz77 said:
Anything
but most likely cache or dalvik cache/unclean update procedures. Either cf stuff or ics stuff could also conflicted.
Gb flash was probably nonwipe rom, so stuff from ics rom/cf kernel conflicting with gb stuff. A factory reset in gb, which is safe, ICS not, could have solved that. Update back to ics was probably a fluke, unless the conflicting stuff was overwritten with the ics rom/modified kernel.
Clean procedures safely executed are always best to prevent this. This includes original components unmoddified for otas and kies update ability.
Off topic tip: efs backup, cause that seriously go wrong with updating.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ahh yes, I have the EFS backup already and its copied everywhere.. LOL
letters_to_cleo said:
Recently there were some minor updates from LRQ streamlined to the phone itself (which has LRQs installed already), these minor revisions (some says) increased the performances of the phone itself.
1. Yes that small update was for the LRQ rom itself... minor updates I should say. The cause on why your phone almost got toasted was and is still unclear to me though. It could be perhaps your phone was never toasted.. You should have perhaps waited more than 5 minutes before.. I'm sure it would have booted up still. But I guess the fact of the matter is,, you panicked after that (after seeing the Note's Logo for 5 minutes only)... He'll I've seen and even experienced my phone to boot up (after flashing a custom rom) around 10 minutes tops... but I did not get fidgety or panicky about it... I guess you may have just push the panic button all too soon bud... You could have waited perhaps even like 8 mins to really verify if it already stucked on the boot logo thing...
2. Going back to Stock GB does not WIPE your phone clean.. you have to initiate really a manual wipe once your in stock GB.. WIPE data/partition, dalvik cache... that is to me the surefire way to wipe clean all the cluttered remnants of the previous ROM you've used before.
Click to expand...
Click to collapse
1. Hmmmm maybe you are right about waiting longer than 5mins.. But i cant say i panicked.. because I just thought that its only a 5mb update so it should not take long to reboot.. I just thought that theres a problem because it did not bother showing up the boot animation so it means it cant pass the proper boot up sequence to proceed with the android update.. (feel free to correct me.. its just my own understanding )
2. Yes I am aware that flashing back to GB cant wipe the data/cache/dalvik but it should wipe out the kernel and any other problems that would keep it from booting into recovery.. but it didnt.. flashing back to GB should give me the stock GB recovery and i should be able to boot to recovery but i failed..
nokiamodeln91 said:
Yes the OP was on LRQ and he got an OTA of 5MB which i meant was the update for LRT
Country/Carrier Date Final PDA Size
Germany 7 Sep 2012 N7000XXLRT 5.7 MB
Click to expand...
Click to collapse
Lesson learned.. Never do OTA updates EVER! :silly:
Thanks for the response guys! But i still have that question in the back of my mind.. What really happened on that update...? My strong guess is that CF root kernel did not like the update since its meant for an LRQ rom not for an LRT..
Edit:
How do I Edit the thread title to add [solved] to it???
Cant see any button that would help.. LOL
to update on OTA u need to be unrooted on stock kernel. then the ota seems to work finr
Sent from my GT-N7000 using xda premium
---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------
capitansid said:
How do I Edit the thread title to add [solved] to it???
Cant see any button that would help.. LOL
Click to expand...
Click to collapse
edit the first post
Sent from my GT-N7000 using xda premium
@captain sid....
it's better to stop getting OTA updates from now on... Kapish? do what you gotta do... if you wanna update your phone... two ways.. KIES or PC Odin. that's all.
nokiamodeln91 said:
to update on OTA u need to be unrooted on stock kernel. then the ota seems to work finr
Sent from my GT-N7000 using xda premium
---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------
edit the first post
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
letters_to_cleo said:
@captain sid....
it's better to stop getting OTA updates from now on... Kapish? do what you gotta do... if you wanna update your phone... two ways.. KIES or PC Odin. that's all.
Click to expand...
Click to collapse
Yeah.. Learned that the hard way.. :highfive:
Related
UPDATE: this thread is closed as Entropy512 has already updated his post and confimed the problem
**moderators, pls remove this post if you want to, since it has been added in the sticky post
thx for those who chose to read this and decided on thier own what to do next
thx for those who kept silent, either like or dislike this post
thx for those claimed they have reformatted the device so many times but still running, but pls report if it failed one day. i am not hoping that ur phone will be bricked, instead, just to inform us what caused it
thx for those against this post with spams, even with possible personal attacks. i learnt a lot of english words
lastly, after the experience this time, it further urges me that this is not the place for me
good luck to u all
FROM THE MODERATOR : This news is not new, and YES you should all take great care when flashing. DO YOUR RESEARCH......... do not flash custom roms without the proper knowledge to do it safely (duh)......
Very few people have had any issue with bricking (I only know of 2)......
BUT do Your Homework........ Oka1 Moderator
FWD: by chainfire:
WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !
Deleting large files while fully booted may also cause problems with your flash memory.
Also see: http://forum.xda-developers.com/showthread.php?t=1633943
Say tuned for further information.
original post by chainfire: http://forum.xda-developers.com/showpost.php?p=19030788&postcount=6 --- This is 6 months old hardly current information....... food for thought- oka1
incorrect link used above. the correct one should be
http://forum.xda-developers.com/showthread.php?p=25966147#post25966147
EDIT: some ppl in the general thread talked about even OTA upgrade is affected. can someone pls confirm this to other ppls here?
EDIT2: for the sake of safety, i suggest NOT upgrading to LPY until the problem is solved and confirmed
EDIT3: so???
what does it mean?
- you risk bricking your phone if u use the LPY rom
- at this time, the exact problem areas are to be determined
- no evidence so far if this is due to cwm or cfroot's, or it could be the stock rom
- if you r still using gb (android 2.3.6), it is suggested to stick with it at the moment
- it is "assumed" that it was due to formatting the partitions in the recovery
- wipe is NOT safe as well. i checked the source and found that a wipe will call the format_volume function, ie to do a format
is it safe to go back to gb?
- all i can say is, gb should be safe. but the problem is, how to get back to gb safely
can i flash a gb via pc odin?
- yes, you can. but again, no guarantee
is it safe to upgrade via pc odin or OTA?
- no one can assure u it is safe
- some ppl reported the phone bricked via OTA upgrade. maybe he was using a leaked one before but yet to confirm
it's only 5-10% failures so why should we concern about this?
- it's simple. u will only realize u r a victum after your phone bricked
- what we know is the number of ppl suffered. what we will know is the number of ppl who suffered avoidable issues after reading this post. but what we dono is how many lives we saved
my phone is working fine with LPY now. i cant see any problem
- as i said, u wont know what's next. perhaps u r lucky and i am lucky too, for now
what to do then?
- sorry, i want to know too. just wait and see what happen
so r u bxllshxting?
- i dont and wont mind if you think so. this is JUST A WARNING. you certainly have the final say whether to be alerted or simply ignore this post
* to moderators
even i will be banned, i will still post this to let ppl be aware about this
but its ok to use on its own....LPY
Will we ever get rid of this hardbricking issues, well how unlucky we are with this, this is getting ridiculous...
vinokirk said:
but its ok to use on its own....LPY
Click to expand...
Click to collapse
ppl in the gerenal section mentioned even OTA has this problem, although i cant proof it
ICS for Note seems to be star-crossed....
I just went back from Stock ICS by flashing Abyss first, though I wiped from with-in CF-LPY kernel no issues, restored a nandroid of Stunner. Everything seems to be working fine.
Also this shouldn't be in Development. IMHO.
OK then I "say tuned for further information"
This is a officiele kernel so no bugs, problem is ower cwm and the things that we do with the phone that a normale person not do with a phone. Xda devs are not fully understanding ics and they tread it like a gb. See all ics threads that post this rom have problems.
Ok so now im.on alba ics with lpy kernel. How do i get back to gb. Use pc odin and flash the gb firmware that doesnt cause triangle and increase cojnter??
Sent from my GT-N7000 using Tapatalk 2
robertberma said:
This is a officiele kernel so no bugs, problem is ower cwm and the things that we do with the phone that a normale person not do with a phone. Xda devs are not fully understanding ics and they tread it like a gb. See all ics threads that post this rom have problems.
Click to expand...
Click to collapse
ppl claimed OTA is affected
also, official rom doesnt mean bugs free
huzz said:
Also this shouldn't be in Development. IMHO.
Click to expand...
Click to collapse
9 out of 10 ppl came here just for download roms. i don care if it's not for development
if we don inform ppl about this, we are not a responsible developer
****in ****, was waiting so long for official ics and now it seems to cause bricks, damn. But thnx for the info, wont be using cwm recovery
so if i flash stock rom via pc odin and dont root it will all be good?
i dont need root just want ics
DNK13 said:
so if i flash stock rom via pc odin and dont root it will all be good?
i dont need root just want ics
Click to expand...
Click to collapse
I think so, yes.
I am using the official ICS and I have flashed CWM. No issues. I used CWM for full backup nandroid. Nothing is strange.
Sent via Galaxy Note
EdgaBimbam said:
****in ****, was waiting so long for official ics and now it seems to cause bricks, damn. But thnx for the info, wont be using cwm recovery
Click to expand...
Click to collapse
Feel the same too...waited so long!! Yeah it seems its not a problem with the ICS kernel per se, but an incompatability with CWM. So we could technically still use the roms as long as we don't use CWM functions/recovery at all. Anyone confirm?
Yesterday, I was afraid to brick my GNote after installing ALBA LPY directly from Kingdroid V7.
First boot and Blocked in Home without any choice to remove battery.
Second boot, same... I installed it without fullwipe.
So Fullwipe from CWM and format /system partition... hanged... and hard reboot
Formatting /system was impossible...
Restore my nandroid backup... Hanged on /system... ouch...
Boot with CWM (franco.Kernel now)... Restore OK...
iT iS Me said:
I am using the official ICS and I have flashed CWM. No issues. I used CWM for full backup nandroid. Nothing is strange.
Sent via Galaxy Note
Click to expand...
Click to collapse
i have no problems too, but i was a victum before and hard bricked my note
Maybe the main reason of bricks LPY is flashing from leaked ics roms? I cant believe about what is happening :O
ykk_five said:
ppl claimed OTA is affected
also, official rom doesnt mean bugs free
9 out of 10 ppl came here just for download roms. i don care if it's not for development
if we don inform ppl about this, we are not a responsible developer
Click to expand...
Click to collapse
you don't need to justify yourself - you did the right thing to open this thread imho!
ykk_five said:
FWD: by chainfire:
WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !
Deleting large files while fully booted may also cause problems with your flash memory.
Also see: http://forum.xda-developers.com/showthread.php?t=1633943
Say tuned for further information.
original post by chainfire: http://forum.xda-developers.com/showpost.php?p=19030788&postcount=6
EDIT: some ppl in the general thread talked about even OTA upgrade is affected. can someone pls confirm this to other ppls here?
EDIT2: for the sake of safety, i suggest NOT upgrading to LPY until the problem is solved and confirmed
* to moderators
even i will be banned, i will still post this to let ppl be aware about this
Click to expand...
Click to collapse
so do you mean that flashing the whole CUSTOM rom with no root and cwm from xda or sammobile is not dangerous? is this what u mean pls reply so that all can know
Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!
marcelo.ellmann said:
Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!
Click to expand...
Click to collapse
ALWAYS flash a GB Kernel or ROM BEFORE flashing a CUSTOM ICS ROM.
Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.
marcelo.ellmann said:
Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.
Click to expand...
Click to collapse
Because of an eMMC brick bug!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
The guide I followed is from here take a few moments to read and understand then you will have no troubles in rooting/flashing again!
hing98 said:
Because ICS has not been officially released on the Galaxy Notes therefore we use a GB Kernel or ROM before we flash any custom ICS ROM.
Yes it was confusing at the start but to avoid bricking you must alwaysfollow the guides given by the Developer!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
Click to expand...
Click to collapse
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium
stoney73 said:
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sorry was reading from another guide. Your right
---------- Post added at 01:12 PM ---------- Previous post was at 12:23 PM ----------
hing98 said:
Sorry was reading from another guide. Your right
Click to expand...
Click to collapse
Anyways its a bug that bricks your device,
you can find more information here
Cheers
I had a galaxy S where flashing process was different Wen u flash CM9 roms and if you want to get back to GB roms only way out was PC Odin and moreover you can wipe on ICS roms and install other roms. But wen i got the note the procedure was slightly different Brickin problems and moreover wen you are in ICS you can get back to GB with GB kernel only no need for PC odin. Just keep a copy of Abyss kernel 4.2 in your sd card and be sure to flash it when changing roms.....
Doesn't Franco rev3+ solve the brick bug?
Hi all,
since you're saying we have *always* to flash a GB kernel before having a factory reset, are you talking about those having the CF/Stock kernel?
I'll make it clear: as far as I know, Franco made a kernel that should avoid the brickage since its 3rd version (thread here --> http://forum.xda-developers.com/showthread.php?t=1491428). Who installed this kernel could just wipe from ICS and install any ICS ROM. Am I wrong? If so, please explain the whys.
UNBRICKED!
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.
Hey guys.. My System Version is listed as being 6.13.215.XT894.Verizon.en.us. (This phone is about a week or 2 old for me) I have installed safetsrap recovery just to see how it works etc and have successfully installed the Eclipse port on the non-safe system. Now that I am done having fun with that, I would like to upgrade my system to newer leaked versions. My question is this: Should I uninstall safestrap before attempting to flash any of the leaked updates? How should I go about removing safestrap the "best" way? Also could someone please enlighten me with the correct "order" of these releases? EG: 6.11.200, 6.11.202, 206 etc. I guess I'm confused bc my system version starts with 6.13 instead of 6.11. Any help much appreciated!
I'm in the same boat as you, safestrap w/eclipse setup and I think I want to just switch to ICS 211
Pretty sure there are 2 methods, one with fastboot, and one with safestrap.
Fastboot method (droidforums.net/forum/droid-4-roms/212634-simplified-211-update-guide.html) definitely requires you to uninstall safestrap, but I think that automatically happens when you flash w/stock 219.
Safestrap method (droidforums.net/forum/search.php?searchid=4780372) allows you to just use a 211 ICS rom. But, I'm not sure if you already have to have done the fastboot ICS, I think you may have to fastboot ICS then install safestrap and safestrap into 211 ICS from 206 or 208 ICS.... Anyways, that's about where I am right now, trying to figure out if I safestrap to a 211 ICS rom from my current stock 219 GB, will it brick my phone. :/
---------- Post added at 12:46 PM ---------- Previous post was at 12:38 PM ----------
Oh also (droidforums.net/forum/droid-news/212864-another-ics-leak-here-droid-4-maybe-closer-ota.html) says that "212 ICS should be leaked soon". You may want to just hold tight, lots of new leaks means that something big (and easy to install for noobs like me ) may be coming soon .
The adventure continues...
Thanks for the quick response man... I'm glad to see I'm not the only one in this situation! I've been "creeping" on this board for 2 years now, (which I can't believe how fast that time went by) and thought it was about time that I start posting etc... you know what I mean, I see that was your 4th post so, that makes 2 situations where we are in the same boat! Thanks for the links brother I have actually read those, but need to checkup on them again... ALSO, my system downloaded an update the other day, (OTA) and was automatically going to install it (I clicked on download, thinking it would just download and wait for me to do the install manually like i have been used to in the past...) So, I tried to interrupt the download by throwing my phone into airplane mode really quick and then forcing a shutdown. Next time I turned on my phone I end up seeing the "Green Android with a triangle" screen, and a progress meter.. and I KNOW what that means. Something was flashed automatically by the phone. I got nervous, but my phone booted up perfectly, and I still had root, along with safestrap intact. I'm still a bit confused by what might've happened, but am relieved that my phone is still working perfectly... strangeness. I'll update this thread w any more info I can find. Thanks again!
Time out guys! First off, you cannot flash the ICS leaks in safestrap. The leaks are updates, not full ROMs. Second, you cannot flash a ROM based off the ICS leaks in safestrap unless you update you stock system to an ICS leak first. Well, you probably could, but it wouldn't boot. If you are on GB .215 you will need to update to .219 first. If you are on GB .219, and have not installed safestrap, you should be able to flash the an ICS leak via stock recovery without fastbooting. If you have installed safestrap, I believe you have to fastboot using the .219 file since safestrap changes something in the build.prop that will cause the leak update to fail.
The Optimizer said:
Thanks for the quick response man... I'm glad to see I'm not the only one in this situation! I've been "creeping" on this board for 2 years now, (which I can't believe how fast that time went by) and thought it was about time that I start posting etc... you know what I mean, I see that was your 4th post so, that makes 2 situations where we are in the same boat! Thanks for the links brother I have actually read those, but need to checkup on them again... ALSO, my system downloaded an update the other day, (OTA) and was automatically going to install it (I clicked on download, thinking it would just download and wait for me to do the install manually like i have been used to in the past...) So, I tried to interrupt the download by throwing my phone into airplane mode really quick and then forcing a shutdown. Next time I turned on my phone I end up seeing the "Green Android with a triangle" screen, and a progress meter.. and I KNOW what that means. Something was flashed automatically by the phone. I got nervous, but my phone booted up perfectly, and I still had root, along with safestrap intact. I'm still a bit confused by what might've happened, but am relieved that my phone is still working perfectly... strangeness. I'll update this thread w any more info I can find. Thanks again!
Click to expand...
Click to collapse
Yup, same here, I'm just taking as much info in right now as possible. I think our options are eclipse, stock 219 with frozen apps, or ICS. Oh if you use stock at all, I'd recommend upgrading to 219, I think that was a major update, my battery life has just about doubled... then again I only had my phone for about a week before upgrading, and about 3 weeks total now.
kwyrt said:
Time out guys! First off, you cannot flash the ICS leaks in safestrap. The leaks are updates, not full ROMs. Second, you cannot flash a ROM based off the ICS leaks in safestrap unless you update you stock system to an ICS leak first. Well, you probably could, but it wouldn't boot. If you are on GB .215 you will need to update to .219 first. If you are on GB .219, and have not installed safestrap, you should be able to flash the an ICS leak via stock recovery without fastbooting. If you have installed safestrap, I believe you have to fastboot using the .219 file since safestrap changes something in the build.prop that will cause the leak update to fail.
Click to expand...
Click to collapse
Thanks for clarifying that ^^, kwyrt, I've read some of your other posts they are always quite informative!
Glad I could help! There are a LOT of nice, helpful people in these forums. Just keep asking questions! Doing some of this stuff can be nerve wracking even if you know what your doing. I actually, finally, got up the nerve to jump on the ICS leak train last night. If you decide to take the leap, I highly recommend using jsnweitzel's Droid 4 Utility located here: http://forum.xda-developers.com/showthread.php?t=1714596. Made the process much easier than it has any right to be.
Android 4.0.4 flash Success! =)
So I decided to take the leap last night... first thing I did was every way of factory resetting I know how to do hehe. (Privacy, factory reset under settings, then a data and dalvik clear in recovery) Downloaded the GB219 file, put it on my SD, fired up the Droid 4 Utility (thanks to everyone who contributed!) and had no problems at all upgrading. I wasn't worried about root so I skipped the OTA rootkeeper process. Next I needed to get to an ICS build. Again, I used the Droid 4 utility.... only difference being that we had to flash the boot.img file first.. (ICSFIX.img). On my first go, I successfully flashed the new boot.img (ICSFIX), but then got a sig verification error when trying to flash the OTA zip. ****. Soft brick at 2AM... heh. at least I still had plenty of time. Re-DL the OTA file, copied it over again and repeated the entire procedure, this time with success. Really Glad I decided to upgrade! Thanks guys!
Stock Rooted OTA 4.08.605.15 710RD Rom
OUTDATED: NOT THE LATEST STOCK VERSION!! 4.08.605.19 is now available.
Thanks goes to soniclude for the ota pull.
Stock Rooted OTA 4.08.605.15 710RD rom. It is rooted, zip aligned, has busybox and comes in odexed or deodexed versions. Other than that it is untouched. Enjoy
[standard flashing disclaimer here]
Wipe everything in the mounts and storage menu in recovery, except sdcard and emmc. Then flash like any other rom.
DOWNLOAD ODEXED - MD5
DOWNLOAD DEODEXED - MD5
If you want a little more customized and tweaked rom check out Touch Of Blue, also updated to 4.08.605.15. Touch Of Blue v2.2
Current OTA or a leak?
nfiniti9 said:
Current OTA or a leak?
Click to expand...
Click to collapse
Latest ota that is being delivered in groups to people as we spaeak. This is a pull from someone who recieved the update yesterday.
?
What are the instructions on how to install this Rom? Wipe everything just like wildstang83s Rom.
ironside2011 said:
What are the instructions on how to install this Rom? Wipe everything just like wildstang83s Rom.
Click to expand...
Click to collapse
Correct, i think. It is probably safest to wipe everything, but might be able to be flashed over wildstangs rom.
cool
I'm gonna wipe everything. I've experienced 1 too many bootloops and hicupps specially with cyanogenmod. My Dinc just never seems to like those Roms
Thank you for this. Been thinking of going to a more stockish rom. The latest roms just have too many bugs and quirks for me.
Sent from my ADR6300 using xda app-developers app
1 more
I literally flashed over wildstang83 Rom . I'm gonna attempt another try but wipe the cache and delvik 1st. Wiping everything didn't do anything. I'll report back soon
Not booting..
Not getting to boot animation... I have tried 3 times now.. Wiped everything..Format boot/storage etc... Anyone get it to work?
I was actually surprised and excited to see this update this morning but thought it would be ICS.
Long ago I rooted my phone just for gaining control and removing bloatware but ended up flashing my first rom with WildStang's Gingerbread OTA. After that I applied the "Warm" theme and been happy with that thinking there would be no more updates to this phone.
To the point - my question for you all is what do you mean by flash over? When the OTA is pushed is it just a patch or do they somehow send and entire install which removes the previous version, saves your data, installs the new version, and puts back your data? I don't have a problem with wiping and starting fresh, and it sounds like that is what everyone is recommending, I'm just trying to understand how it would even work flashing "over" my current version.
Nobody has replied to my post and I have not seen anyone report a trouble free install here so I'm gonna sit on the fence for a while
Did a full wipe and all seems to be working well
?
Just downloaded VR superwipe. I'm gonna redownload this Rom and give it another shot.
wrigbone said:
I was actually surprised and excited to see this update this morning but thought it would be ICS.
Long ago I rooted my phone just for gaining control and removing bloatware but ended up flashing my first rom with WildStang's Gingerbread OTA. After that I applied the "Warm" theme and been happy with that thinking there would be no more updates to this phone.
To the point - my question for you all is what do you mean by flash over? When the OTA is pushed is it just a patch or do they somehow send and entire install which removes the previous version, saves your data, installs the new version, and puts back your data? I don't have a problem with wiping and starting fresh, and it sounds like that is what everyone is recommending, I'm just trying to understand how it would even work flashing "over" my current version.
Click to expand...
Click to collapse
Flash over is just how it sounds. Literally flash on top of your current rom without wiping your data out.
Sent from my ADR6300 using xda app-developers app
If you want to go completely back to stock can you ruu back to 605.2? Then re ota to .15?
Topsnake said:
If you want to go completely back to stock can you ruu back to 605.2? Then re ota to .15?
Click to expand...
Click to collapse
Yes
I have a question.
I am running an ICS ROM how does this affect me....
Well my QUESTION is this:
What are the procedures to installing this and can I just reflash the ICS ROM I was on before.
The only updates with this push seem to be SMS and Bluetooth, is it even worth it?
Thanks for your time guys....
I performed a data/factory reset, cleared the cache partition as well as did a dalvik wipe but after installing it gets stuck on the white Incredible screen. Any ideas? Perhaps my kernal/radio? I honestly lost track of what kernal and radio I have so I am not sure.
So what's up with this ROM, I flashed like 3 times And it boots up.....then it starts a random reboot and just bootloops continuously. Is there any fix?
EDIT: seems the OTA update was a bust check this out........
http://forums.androidcentral.com/ve.../182357-dinc-system-update-4-08-605-15-a.html
Sent from my Galaxy Nexus using Tapatalk 2
@ cmlusco
So guy - you put this out here and it seems like everyone is having problems. How about some feedback. I'm getting ready to sell this phone in two weeks and want it to be on the current version but I'm not touching this ROM until I hear it freakin works. There are always a few people with issues but I'm not hearing anyone saying "flashed it and running with no problems". Appreciate the effort to get this out there but if your gonna take the time follow through on your commitment.
Hi Folks
Im a new proud owner of a Note, just got it today and loving it so far, waiting for JB in March though .
Ive checked and my Note has the "YES insane chip", however, i only flash Stock roms through odin and use Stock recovery after each flash, so am I right in reading that its only custom ROMS and Kernels that can brick it, so I never have to worry about it bricking or is there something i should be careful of when flashing stock roms as well.
Thanks
No, if you wipe your data through a factory reset there is a high chance in bricking the device.
XxPixX said:
No, if you wipe your data through a factory reset there is a high chance in bricking the device.
Click to expand...
Click to collapse
Oh.. wow, how can Sammy release hardware like this then, thats pretty bad. I take it the New S3s and Note 2s dont have thiese chips then.
Cheers
Samsung claims, that recent stock recoveries are safe, no one knows for sure if that's true.
If you want to be absolutely safe, use a recent custom kernel, those are known to be safe, since they completely disable the broken erase function.
guv. said:
Samsung claims, that recent stock recoveries are safe, no one knows for sure if that's true.
If you want to be absolutely safe, use a recent custom kernel, those are known to be safe, since they completely disable the broken erase function.
Click to expand...
Click to collapse
I did a factory reset > wipe Cache earlier and it booted ok thankfully. Im on UK XXLRK 404 (July 2012) so how recent do Samsung mean, but it seems to be on all 404 Roms (s2/Note), but thanks for the heads up... can I just say though that I would Never "Factory Reset" through Settings because im not sure if it wipes the cache or does much really, also the next and only update ill be doing will be JB 412 in March, if it arrives
Cheers
Can I just ask, when JB comes out in a few weeks, would you recommend to flash a safe kernel first, then update to JB.. or because Im Updating, should I just flash straight to stock JB in ODIN, then reset through Stock Recovery.
EDIT:
Also, Im new to this device so could anyone recommend a safe fast kernel to use with a stock 404 Rom.. Unrooted
Thanks
speedmod, Philz, hydracore.. all are safe
if you are not rooted then update via kies. or via odin.. dont do reset in stock recovery of ICS... or JB yet as not yet confirmed safe.. may be after the sources come out.. one of the devs can confirm it
I was trying my hands on ubuntu from paranoid, but flashed ics, and mistakely i didnt wipe anything before flashing,so i did wipe on ics kernel, so it was stuck on bootloop ,but i could enter recovery and download. so i first flashed philz kernel and did a wipe and downgraded to gb. So i want to know is this the emmc brick bug or a soft brick..
so if your phone is working you were lucky..
nokiamodeln91 said:
so if your phone is working you were lucky..
Click to expand...
Click to collapse
Ya my phone is working but what kind of brick was this. i have read about emmc brick bug but couldnt get what is it.
A soft brick
Sent from my GT-N7000 using Tapatalk 2