Related
Sorry, this has I'm sure been done to death but there seem to be conflicting reports and advice would some kind soul, who knows the answer, tell me.
I think I know the answer but I don't want to take a chance on it ;-)
Sent from my GT-P6800 using Tapatalk 2
Yes the safe answer is that nothing is for sure at 100%...
I asked the same and despite I mentioned I will cool down trying stuff I did actually try quicksilver.
Initially I've reset once INSIDE ICS after the first installation going from HC to ICS without trouble
Then before trying quicksilver I did nandroid backup after that I purposely wiped reset using CWM 5.0.0.4 from dev but also wiped cache as well as dalvik and battery stats... Then restored the backup... All those could trigger a brick but it did not
Next I wiped again everything via CWM reset and installed quicksilver 0.8 and all went fine booting quicksilver.
Then updated to 0.9 and finally 1.0pre doing that did not require wipe so did not do it for no reasons...
Then went back restaurant my original backup.
So I did not have any problem this in no way means it is 100% safe as you I am worry but decided to try knowing something could go wrong. From now on I will only reset from CWM 5.0.0.4 and will not do from ICS
Sent from my GT-P6800 using xda premium
Hmm could be nandroid problem redo all steps but dont make a backup.
Sent from my GT-P6800 using xda premium
Deleted. This question isn't useful.
@questionmark factory reset from the latest CWM. No issues.
Sent from my GT-P6800 using Tapatalk 2
I did factory reset many times with Austrian ICS Rom with no problems at all , it's is safe
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not be able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
altae said:
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
Click to expand...
Click to collapse
I have never considered the "hex-patched" kernels to be safe...
jeriz said:
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
Click to expand...
Click to collapse
Yep. I don't think the drivers are the problem since the phone is recognized. But it does not start to flash. It simply does nothing and the phone stays in download mode forever.
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
this in itself is a huge statement
altae said:
I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash.
Click to expand...
Click to collapse
This is diferent... not even start to flash...
Sent from my GT-P3110 using Tapatalk 2
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
It seems that remaining on Gingerbread (until official JB) for the moment is the best thing for people who do not have a warranty for their Note.
Many people confuse superbrick (phone dead right away, no life even if you plug a charger) and other bricks. This is just an unfortunate other brick not related in any way to emmc described one. Good luck at RMA
Also, copying big video to your sdcard is a good way to kill it. Old i9000 thread was popular with that
Sent from my GT-I9100 using Tapatalk 2
Was running Paranoid Android
Tried to restore the Note back to the latest UK stock ICS ROM via ODIN
Forgot to wipe/davlik before hand
then got stuck in boot loop
more boot loops
Then tried flashing a rooted GB rom in ODIN
stuck now on the Samsung Note boot screen occasionally looping.
Then tried flashing an original non-rooted GB rom in Odin
got stuck on Data.img
Then tried again and it stuck on FACTORYFS wont even get passed this.
Took battery out, then back in...
Now the screen shows three images and the message
firmware upgrade encountered an issue
Now with the Samsung Repair centre in Eastbourne and they are failing to be able to do anything...they still have my NOTE:crying:
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
Sure, you can theorically miss the binary check in rare circumstances. But this is just "an other brick" without any common relation typical to described emmc brick: no wipe, no flash, and mainly no right away (or even) complete dead phone
Sent from my GT-I9100 using Tapatalk 2
@ Entropy. Even guy above Phil3759 his bricked his note starting from PA which has a "safe" kernel, and eventually superbricking just useing PC Odin (long time considered safe). No wipes involved. Anyway, is Tungstwenty's detection method flawed for stock ICS kernels? Or is there are problem changing the offending byte from a 1 to a zero
Sent from my GT-N7000 using xda app-developers app
At least this brick has made me decide to leave my note well alone, after flashing roms practically daily for the last month or so, I have become insanely addicted to changing roms...once i get the Note back from the Sammy Service place, I am sticking with stock and wait till the official JB update arrives, which looks fantastic.
As it states on all these roms flashing custom roms at your own risk, thus its my own fault, finger crossed it can be sorted.
You can brick any phone, it happens, yes. Superbrick related to emmc bug occurs under special circumstances with typical symptoms.
Binary patching kernels, in theory, if you happen to have duplicate binary code or different, you could miss it. But, as far as i know, and for all manual checks i did, it never happened...
Sent from my GT-I9100 using Tapatalk 2
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Markuzy said:
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
As i said, it is really non recommended to use your internal sdcard for regular heavy write operations like videos. It will be corrupted at a certain point. On the i9000 this used to be a way for some to get warranty. Phone stuck often after a continuous write/wipe overnight
But this is not the superbrick. And one day, all your phones will brick. That's flash storage
Sent from my GT-I9100 using Tapatalk 2
altae said:
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
Click to expand...
Click to collapse
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
shoey63 said:
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
If you read across HTC and other forums, you'll see so much bricks and unhappy people. Why blame Samsung, there will be always faulty devices and unhappy unfortunate people
Sent from my GT-I9100 using Tapatalk 2
Yeah, you're right. Even PC Nand causes grief. Just hoped a Company on the cutting edge of technology like Samsung would have been able to resolve such problems.
Sent from my GT-N7000 using xda app-developers app
I would better trust seagate or corsair to push it further. Samsung HDD always failed on me. Ditched them long ago
Sent from my GT-I9100 using Tapatalk 2
---------- Post added at 11:40 AM ---------- Previous post was at 11:35 AM ----------
By the way, for people that want to know more about binary patching kernels, read here, it is worth it
http://forum.xda-developers.com/showthread.php?p=29609295
Sent from my GT-I9100 using Tapatalk 2
hello everyone.
im new with iconia a501 because its my friend's.
we tryed to update it, but its stuck in bootloop.
update we installed is oficial ota 4.0.1.
everything looked fine untill it rebooted. then system ui crashed. and it keeps rebooting and crashing .
I dont know what to do. I really feel his pain in loss.
sd card is not working, wich is not hellping.
dont have cpuid, so cant flash.
no root or cwm installed or backup...
is there any possibility to revive?
or is there any specialist in uk, who could fix it?
I think I read all threads in xda foroms. and everything I could find in google.
can't apply any method found.
any ideas? or suggestions anyone?
any help is appreciated.
I'd be trying a full wipeto fix System.ui from crashing. If u can not boot, you'll need to factory data reset....reset pin + pwr+ lock switch, tab should vibrate then erase data and cache.
Also boot while holding volume up button...do u see a fastboot menu or "skrilax_cz bootloader" screen...just to see which bootloader is on the tab.
You say sd card won't work.....wot doesn't work..check both sets of drivers are installed. ...Acer and android ones.
Hopefully the data reset will get u going...If not there's still few things we can try.
You can get yr cpuid/sbk thru apx mode using ubuntu, there's a sticky in general forum.
Thank you very much I'll try everything tonight.
Sent from my GT-N7000 using xda premium
smple factory reset did the job. my friend is enjoying his iconia again. now even more tbo
thank you for help again.
case closed.
Sent from my GT-N7000 using xda premium
Awesome news....pls ask yr friend to get the cpuid of the tab, it's the only way of fixing future potential bricks, saves a lot of stress and effort
Sent from my GT-I9300 using Tapatalk 2
I have no explanation of what has happened to my n7. It shut off by itself and just bootloops when I try to turn back on. I can get into recovery and I have a nandroid backup of a stock rom. Everytime I restore it restores system and then fails?? I flashed 3 different roms and all r flashed successfully but I get the same bootloops . I was using latest twrp and was get error I/o data / speedtest. Something else but I flashed cwm touch b4 I could jot down the errors . I figured it was twrp bug and didnt realize I wouldnt b able to flash back to twrp do to using gooim to write the image in the first place. I am desperate to find out what happened and I wont b near a pc for a few days. I have an unlocked rooted grouper version . I have read and searched b4 posting
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
it could be a hardware failure, maybe the mounted drive (emulated sd card) is corrupted and broken? the boot partition seems to be working
It sux cuz I wont have access to a pc for a few days
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
have you tried clearing the whole of /system /data /cache... everything except /sdcard then flash a new rom? maybe that'll clear some things up
Billchen0014 said:
have you tried clearing the whole of /system /data /cache... everything except /sdcard then flash a new rom? maybe that'll clear some things up
Click to expand...
Click to collapse
Yes I wiped system /cache/dalvik/ and factory reset I did them all like 5 times each and flashed a brand new rom. Its so weird
Nothing works. I am always prepared for atuff like this with multiple nandroids cwm/twrp but they both fail to restore
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
Back in a few months ago I'm faced with that problem once, tried everything like factory reset, format system/data/cache/sd, install new ROM and also tried to restore by nandroid backup (that used to work fine before that problem occur) but non of these solutions work.
Finally I've to use fastboot to flash it to 4.1.2 (to format and re-partition the device) and flash it back to 4.2.2 and then it work fine again even with many custom rom and kernel installed to my N7 very frequent and today it still work just fine.
why always me said:
Back in a few months ago I'm faced with that problem once, tried everything like factory reset, format system/data/cache/sd, install new ROM and also tried to restore by nandroid backup (that used to work fine before that problem occur) but non of these solutions work.
Finally I've to use fastboot to flash it to 4.1.2 (to format and re-partition the device) and flash it back to 4.2.2 and then it work fine again even with many custom rom and kernel installed to my N7 very frequent and today it still work just fine.
Click to expand...
Click to collapse
Thanks that is what im gonna have to do
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
Thanks for the advice i got my pc back today and used wugs toolkit to flash factory image and it booted up thank god .
Sent from my Nexus 7 using Tapatalk 4 Beta
bbobarino said:
Thanks for the advice i got my pc back today and used wugs toolkit to flash factory image and it booted up thank god .
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
In the future, I'd refrain from flashing if you didn't have a computer on hand.
Sent from my Nexus 7 using XDA Premium HD app
peneoark said:
In the future, I'd refrain from flashing if you didn't have a computer on hand.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I couldnt agree more but thats the weird thing I didnt even flash anything for like a week b4 this happened thats why it was so bizzare to me. Still cant explain why it did that
Sent from my SGH-M919 using Tapatalk 4 Beta
bbobarino said:
I couldnt agree more but thats the weird thing I didnt even flash anything for like a week b4 this happened thats why it was so bizzare to me. Still cant explain why it did that
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Electronics can be wacky sometimes
I have a note 3 and my awesome kid thought he could mod it for me, the problem is that he said that my phone was in roaming mode so he used terminal emulator and typed something in that he read,now my note 3 was rooted but I cant get it back to stock using odin,its like its stuck in custom mode any help will be a plus thanks
1. Your awesome kid is grounded for 3 weeks. lol
2. Where in the process is your odin-back-to-stock does it fail?
<Note3>
Sorry for the late response in Odin it passed through but it reboots several times and then back to the custom unlock screen to the Samsung logo and to the Verizon logo and it starts all over again
Sent from my SM-N900V using Tapatalk
K. What version was your firmware before you odined, and what version are you odining to? Also, are you using the .tar file and the .pit file in odin? The .pit file will allow you to repartition your phone. Essentially formatting the entire thing before putting the op system back on.
<Note3>
Thanks for replying back 4.3 MJE is on now and for the pit file should I flash that first before I flash an op
Sent from my SM-N900V using Tapatalk
You choose them both and they get applied at the same time in odin. And also make sure the repartition box is checked before you start the odin process.
I can't remember if odin wipes intrrnal sd storage when just flashing the .tar file. But it definitely will when you flash the .pit. So be sure everything you want to keep is on ext sd storage (if you can even do that in your current state).
OK will try report back in a bit Thank u again
Sent from my SM-N900V using Tapatalk
camphurt said:
OK will try report back in a bit Thank u again
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Read my last post again. I added info...
<Note3>
Just to let you know that the one that were working on is my backup note 3 so we're working on just trying to get it up and running I'm on my other one right now
Sent from my SM-N900V using Tapatalk
OK just flash both and I thought all went well it.phone began android updating but it went back to custom boot screen then reloaded back to process isn't responding
Sent from my SM-N900V using Tapatalk
1 question, 1 request, and 1 suggestion.
(Q) After you applied the Odin PIT & MJE flash ( I presume you are using ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5), does the phone go into the recovery boot the very first time it rebooted?
(R) Please post (cut-n-paste) the log messages from the Odin flash session if you repeat it.
(S) You might try holding the power button down for 9 seconds to power off the phone; then, hold down Vol-Up+Power to boot the phone into the stock recovery, and perform a factory reset there. This might not cure the bootloop problem, but it is possible that it will eliminate the "custom" screen during boot. Since you are still showing the Knox Warranty flag at 0x0, that would make a warranty return possible.
Note that there are 16 partitions on the phone which are not replaced by flashing a stock firmware in Odin. (for instance ddr, pad, param, efs, modemst1, modemst2, fota, backup, fsg, fsc, ssd, pad, param, efs, persist, persdata). 3 of these are actually mounted by the stock ROM - efs, persist, & persdata.
The reason that I mention this is because it is quite possible that restoring a factory ROM will not fix your phone. Without some idea of what you (or others) actually did to your phone, there are a limitless number of things that could have possibly gone wrong.
good luck... and please do not open another thread on this same topic - it is a violation of the rules here.
Like I said I was sorry about being a pest didn't mean to break the rules and I apologize for that I was just looking for help so thank you.. The phone was just a backup anyway
Sent from my SM-N900V using Tapatalk
camphurt said:
Like I said I was sorry about being a pest didn't mean to break the rules and I apologize for that I was just looking for help so thank you.. The phone was just a backup anyway
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Deleted