Related
i have to send my infuse in under warranty, so which verison of stock should i use?
i know att will want me to have the most current operating system installed when i send it in.
thanks guys
I would just flash gtg's unbrick and the search updates under settings.
Sent from my SAMSUNG-SGH-I997 using XDA App
After using unbrick, restore to factory once booted so that it will hopefully erase all traces.
Cranky...
shg-i997uckh1
but you might want to flash ke3 and find a bootloader dump from it. if you updated to current bootloaders i believe it has a counter for number of 3rd party firmwares flashed to it. dont want the insurance company to see that. i dont know if this coulter counts cwm flashes or just download mode flashes but it somewhat can distinguish between att official and not atleast on the kernel end.
The title pretty much says it all, I am running rooted rogers stock, and recently my phone has stopped connecting through usb. I have tried on multiple computers and on each one, thr phone just charges when connected, i dont get a notification saying that usb is connected, nothing. I am not using the cable that came with my phone as i have lost it, but the cable im' using worked fine in the past (its a kindle usb btw). I am wondering if theres any way to fix this, or am I SOL?
Sent from my SGH-I727R using XDA
Try to install the latest Samsung USB Drivers.
Also you can try plugging it to another computer/laptop, if it doesn't work either then there is a chance that the cord has gone bad. I know my computer doesn't recognize my phone when its on my USB extender but when I use the stock USB cord it detects it fine.
UZ7 said:
Try to install the latest Samsung USB Drivers.
Also you can try plugging it to another computer/laptop, if it doesn't work either then there is a chance that the cord has gone bad. I know my computer doesn't recognize my phone when its on my USB extender but when I use the stock USB cord it detects it fine.
Click to expand...
Click to collapse
I have the latest drivers downloaded, I'll borrow my friends cord on monday, till then I'll scower my house fot my cord. Thanks for the reply!
Sent from my SGH-I727R using XDA
I had the exact same thing happen to me. Went to the AT&T repair facility and got it swapped out. You can find out where the closest one is from a retail store. Since Galaxy is so new, you probably shouldn't even need your receipt. If you are rooted, I hope you have a stock NANDROID backup of unrooted stock. I was afraid they would deny so I unrooted. Since I didn't have a NANDROID, and didn't want to flash ODIN and trip the counter, I ended up having to make a CWM flashable zip of stock, including stock recovery, using WIFI to transfer the file, and flash. I heard many tech don't care and will swap out for you either way. Hope you get it swapped w/o hassle!
freakius said:
I had the exact same thing happen to me. Went to the AT&T repair facility and got it swapped out. You can find out where the closest one is from a retail store. Since Galaxy is so new, you probably shouldn't even need your receipt. If you are rooted, I hope you have a stock NANDROID backup of unrooted stock. I was afraid they would deny so I unrooted. Since I didn't have a NANDROID, and didn't want to flash ODIN and trip the counter, I ended up having to make a CWM flashable zip of stock, including stock recovery, using WIFI to transfer the file, and flash. I heard many tech don't care and will swap out for you either way. Hope you get it swapped w/o hassle!
Click to expand...
Click to collapse
All you need to do is flash the counter reset and Odin the sammobile tar
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Could also be an issue with the cable. Had similar issues before switching to a new one.
I had the exact same thing happen to me. Went to the AT&T repair facility and got it swapped out. You can find out where the closest one is from a retail store. Since Galaxy is so new, you probably shouldn't even need your receipt. If you are rooted, I hope you have a stock NANDROID backup of unrooted stock. I was afraid they would deny so I unrooted. Since I didn't have a NANDROID, and didn't want to flash ODIN and trip the counter, I ended up having to make a CWM flashable zip of stock, including stock recovery, using WIFI to transfer the file, and flash. I heard many tech don't care and will swap out for you either way. Hope you get it swapped w/o hassle!
Click to expand...
Click to collapse
How would u make a flashable zip like that?
Sent from my SGH-I727R using XDA
Does anyone know how to do what freakius did with rogers stock?
Sent from my SGH-I727R using XDA
thatguy97 said:
Does anyone know how to do what freakius did with rogers stock?
Sent from my SGH-I727R using XDA
Click to expand...
Click to collapse
Rogers tar is in the unbrick/unroot thread. Rogers is waaay more lenient than AT&T, and I don't most know what rooting even is
icenight89 said:
Rogers tar is in the unbrick/unroot thread. Rogers is waaay more lenient than AT&T, and I don't most know what rooting even is
Click to expand...
Click to collapse
Read my first post, my problem is that my phone wont connect to my computer through usb so i couldn't flash that tar even if i wanted to
I have the same problem and upon format in cwm it says dev/block unable to.format
There's a similar thread on this in the General section.
http://forum.xda-developers.com/showthread.php?t=1626813&page=2
In short, IMO it's likely a cold solder issue. Have a long conversation with someone (45 min-hour) with the phone in your hand (so it heats up internally) then connect to a computer. If it comes up, you know it's a hardware issue. This was the case with mine.
After the ICS was leaked, it bought some good news and as well some bad news..
Some of our user have just bricked their mobile after performing a wipe data thru recovery..
The cause of error is yet unknown..
Out user vijai has published some of the known causes...
The credit goes to vijai for pointing it out
vijai2011 said:
CAUSES
Symptoms of super brick(caused by emmc bug):
1.Phone gets stuck at splash screen.
2.recovery gets stuck at whenever trying to access corrupted partition.
3.ODIN gets stuck at flashing factoryfs.
4.You can flash kernel but almost nothing else using both ODIN and cwm.
Sent from my GT-N7000 using xda app-developers
Click to expand...
Click to collapse
vijai2011 said:
FIX
No problem....temporary fix to avoid bricking is to avoid using cwm to flash anything,doing wipes in cwm,formatting partitions in cwm,doing factory reset through settings and by typing code in phone,removing large size files from sdcard.
The permanent fix is to disable MMC_CAP_ERASE in kernel while making it.Any kernel dev can do that easily I guess....
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
This definitely doesn't mean that all galaxy R handset are brick bug or you may encounter such problem..
Only a few have encountered the problem and the cause is yet unknown. This definitely, doesn't stop you from flashing ics..if you want to flash keep these things in mind.
Also, please do not completely rely on brick bug app from play store because the app (imo) is not supported to our device (correct me if i am wrong)
(i am no developer, just heard from my fellow user )
*****NOTE******
This applies to the Stock ROM released by machram and as well to all those ROM which are based/built upon the Stock ROM.
Click to expand...
Click to collapse
SO WHAT DOES IT MEANS TO YOU ?
If you have already flashed ICS, you are requested not to wipe data through CWM/Stock recovery and also do not factory reset the phone till the issue is identified. i.e. Once ICS === No Wipe (till its rectified)
Click to expand...
Click to collapse
Currently there are only two users who have hard bricked their phone after flashing ICS.
As you might be aware by now that the emmc brick bug app is not compatible with our phone.
The most elite developer Entropy512 wants to make it compatible and hence wants some sample..
Entropy512 said:
Can someone who experienced damage and still has their device contact me via PM? One of my contacts wants to collect a few damaged devices.
Click to expand...
Click to collapse
Note: I dnt recommend you to brick your phone
(thanks m.kochan, callmeventus, cooleagle)
A big thanks to entropy for showing interest to our device
Caution:
Here's what to say from a user who bricked his phone
mj.vikram said:
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck..
Click to expand...
Click to collapse
*******UPDATE********
Here is the new fix method
vijai2011 said:
And guys for the guide to safe flash:
Flash a GB kernel,boot into recovery,flash any rom.GB or ICS.Its safe to wipe in gb kernel.But once you flashed ICS you arent safe.If you need to wipe again,you need a GB kernel again.
This was the method we used in Note to wipe when had not got a safe kernel.
Click to expand...
Click to collapse
We have got one lucky user who is enough brave and tested this method
selva.simple said:
To make a conclusion to that, i have tested your method in Galax R buddy. I found that i had a GB kernel in my phone. So why wait till i reach home. Tested now itself. I tested two rounds. One is for getting ICS via CWM flash and the other is for getting ICS via CWM restore.
First Test:
1. Flashed GB kernel
2. Rebooted to Recovery
3. Wipe data
4. Flash ICS by CWM flash i.e., "Install from Zip" method
5. Reboot
Second Test:
First Three points are same. and finally Restored a nandroid backup of ICS i took earlier. Reboot
In both the method i was able to boot the phone and get the ICS ROM and ICS kernel. To add more,
After both boots, I tested the system apps and data apps - mainly Play store, Gmail, Music player, Gallery, Camera for any FC issues. Everything is working perfectly and no issues created apart from existing issues of ICS.
Click to expand...
Click to collapse
And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app
vijai2011 said:
And I forgot to add that It is not necessary that brick occurs once you do the above said things....for example,brick may occur at 10th factory reset,100th flash etc....And it is safe to flash anything with Odin as it shouldn't invoke MMC_CAP_ERASE from kernel when flashing.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yes i do agree..d problem may arise on 1st or on 100th wipe...
Bt the cause is yet unknown...
So imho, all the noobs shldnt do..who knows they get it for the first time...
Sent from my GT-I9103 using Tapatalk 2
Seriously? Removing large size files from sdcard can brick my phone?
Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Dont know...but i have tried deleting large files as 1gb game data...such as max payne and asphalt7
No brick...
Sent from my GT-I9103 using Tapatalk 2
Fusrodah said:
Seriously? Removing large size files from sdcard can brick my phone?
Click to expand...
Click to collapse
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app
vijai2011 said:
Yes....sometimes.....it was reported by like 2 users have galaxy Note.While deleting large files,the phone stuck and force reboot caused damaged sdcard.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?
So a little story now.
From where has this infamous brick bug appeared??
Analysis by kernel devs say that MMC_CAP_ERASE command in kernels are present from gb periods.But why hasn't it been causing problems in GB?That's because it was disabled as Google didn't see the need for it.
But in ICS they feel that just removing files causes security problems.so they thought of enabling MMC_CAP_ERASE command which will completely wipe instead of removing.
So why should it need to brick our devices?
That's because,one of the Google engineer said that our mmc uses buggy firmware that initiates wrong process when the kernel receives MMC_CAP_ERASE command.
Actually MMC_CAP_ERASE command and mmc buggy firmware are harmless on its own.But when both are combined the result is super brick.
Sent from my GT-N7000 using xda app-developers app
This is not the worst scenario. In worst case you're gonna get hardbrick with no possibility to turn your device on.
MMC_CAP_ERASE on - wasn't present in every ICS version, at least not for S2 (I know that NOte users had bigger problem with that). All previous 4.0.3 were totally safe. Latest 4.0.4 - unfortunately not. It's not really buggy firmware that causes any problem here. According to Entropy512 (I guess the best xda-expert in that matter) MMC_CAP_ERASE was activated in order to improve writing speed. Hard brick occur if the all three conditions are fulfilled here:
1) You have a faulty (brickable) emmc-chip
2) If MMC_CAP_ERASE command is activated in kernel
3) If you perform wipe/restore nand backup/install roms (wipe-type) where:
a) cwm recovery - very high risk
b) stock recovery - lower risk but still not equal 0.
So faulty emmc chip is a bomb, mmc_cap_erase is a fuse, wiping in cwm - is a trigger or fire!
Not all devices are endangered, only those with brickable emmc-chips. In regard to Note or S2 it's easier because those devices have great dev support and there were thoroughly examined. So there are known some ways to bypass this problem. In case of SGR is much harder. First of all ... we don't know which chips are really sane and which are not.
Fusrodah said:
Well, how much reports from Galaxy R users with bricks? I see one from mj.vikram. Anyone else?
Click to expand...
Click to collapse
Just two as of now so don't panic !
You can use ICS 4.0.4 but till the cause of the bricking is confirmed just don't preform any Wipe data / Wipe Cache / Factory reset operations while on ICS 4.0.4 ROM.
As per mkochan if you want to go back to the stock ROM for giving it to the service center / etc then directly flash GB / 2.3.x ROM without wiping the cache / data using CWM.
m.kochan10 said:
1) To avoid brick = don't wipe, don't do factory reset, do not restore nandbackups.
a) If you wanna to get rid of this fw.version
-> Flash a safe kernel / or best stock rom directly via Odin.
-> Wipe after installation process is done. NOT BEFORE!
2) To recover...one guy from Note section wrote a tutorial for those bricked devices that was able to turn on. He managed to recover it but he had to sacrifice 2-3 gb of internal storage. If device is not bootable then it's a motherboard replacement.
3) Turning off this function in kernel is not easy thing. I don't think this flag can be easily removed. I'm not a kernel guy....so I'm sorry but don't know much more about that. Our devs can take a look, maybe they can find a solution.
4) Bootloaders cannot be flashed via recovery, not via mobile odin either. And FW-odin version is still unavailable so I assume you still have GB ones.
5) About USB jig - Is your DM protocol the same like before? 2.0? (people with 2.1 have never been able to used jig as far as I remember)
Click to expand...
Click to collapse
Okay, we must wait for kernel with disabled MMC_CAP_ERASE. I hope we'll get it. Thanks for the information.
Oh my god
I did factory reset in ics because my keyboard dissappeared. Will my device hard brick?
I cannot understand why Samsung realeses a firmware which should make our mobile dead! What is this function even for?
Sent from my GT-I9103 using xda premium
You can find sort of explanation on the previous page
Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?
Google86 said:
Just wondering should I worry about this if the bug eMMC app reports that I have a sane chip?
Click to expand...
Click to collapse
I think app is not working for SGR, both user have used this app and app shown sane chip yet those both guys devices are bricked.
We should contact dev of app to make comp with SGR.
Sent from my CM7.2 powered Galaxy R using Tapatalk 2.
Damn it , I knew this would happen.....
"Friends forever." - Ventus
Guys actually you could check if you have any bad blocks in any partition through gpartrd in adb.Just looking its info.will post when I find some.
Sent from my GT-N7000 using xda app-developers app
OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Sorry i have't seen this thread and created new one, so if you think i have created duplicate one please ask Justin to delete it....
mj.vikram said:
OP please add this also,
Caution:
when you are running ICS on you mobile do not downgrade directly to GB using ODIN, if you flash any GB ROM ROM (Stock/Custom) using ODIN your mobile will be bricked.
Live example is myself i have bricked my mobile by do this.
TO avoid this first you restore previous backup using CWM and then flash what ever you want using ODIN.
even Unbrick your Galaxy R. 2. Downgrade bootloader to v2.0 guide wont help you, I have followed it but no use I have successively flashed stock rom by using this method but still no luck ..
Click to expand...
Click to collapse
Dude i dont have a GB Backup (CWM BACKUP)
and dude, what you gonna do now, how will you get back your phone ???
Okay so I have just rooted my Samsung Galaxy Precedent Friday running stock 2.2.2 froyo and no updates available... and loved everything I do. I downloaded a rom made for the precedent and named it Update.zip in the root of the sd card and got the Rom Manager app. Then I clicked install rom from SD Card and picked the rom and click wipe Cache and Backup current rom. Then it booted into recovery mode but then the only selections there are Factory Reset, Clear Cache,Reboot Phone, And some other selection saying something about going into a update.zip but when I click I click it, it says Failed and brung me back to the menu. When I watched people boot a rom from the sd using Rom manager non of those selections came up for them. It just installed the rom. And booted. How come I can't do that? Did I do something wrong. If yes someone please tell me the correct way to install a custom rom on the Samsung Galaxy Precedent.
It sounds like you didn't install a custom recovery?
Did you ever install ClockworkMod or TWRP?
Sent from my SGH-T999 using xda app-developers app
No i have not. I've tried to install cwm but never understood it and could not do it. I do not have access to a computer so can you please tell me how to do this without a computer?? Thanks
Honestly, I would tell you to read up and understand it before you do anything else. Flashing ROMs is something that can leave your phone a lifeless brick that you can't even turn on. I feel like if you don't understand what you're doing, it's like telling you how to change a capacitor in a PSU, but not how to avoid being shocked by enough to kill you.
You can install CWM using ROM manager and TWRP with goo manager. Most people who have tried both like TWRP better. I'd suggest you read up on both and pick for yourself.
Bricking will cost you a minimum of JTAG repair costs - and that's if someone knows how and will do it for your phone model. They might not. O'er than that, you have to get a new phone.
Not trying to be a raincloud - but just to warn you that it's a bad idea to jump into a shark tank without some protection.
Sent from my SGH-T999 using xda app-developers app
Isn't there a way I can backup my current rom so that if it does brick my phone I can get my phone fixed??
Yes and no.
If you install a custom recovery you can make a backup, yeah - but you can only restore that if you're, well... Able to. You can brick the phone, like I said - to the point it won't even turn on. A backup won't help if you can't even turn the phone on.
Sent from my SGH-T999 using xda app-developers app
Well what roms are out there for the Precedent or even Samsung Galaxy Collection that ur for sure won't do any harm to your phone?
There really is no "for sure".
Please just do a littke reading and learning and you'll understand what you're doing and the process and how you might choose a ROM (I don't know how popular your phone is or was so you'll need to find out if there are even people doing custom work for it). We can't spoon-feed this to you - there's a quote from Jurassic Park about the danger of trying to stand on the shoulders of giants.
This is like learning to drive a car. Once you know how, you can drive all kinds of cars pretty well - but you need to put in that initial time to learn or it's dangerous.
Sent from my SGH-T999 using xda app-developers app
My USB port is kaput so I need to send my CWM+CM11 blaze for warranty repair. Can't flash via Odin and the only stock room zip I found on the forums is a dead link. Any assistance would be greatly appreciated.
Sorry dude... At this point, you've voided your warranty by changing the firmware, and the USB is the only I can think of to revert back to stock... You have to remove your custom recovery with an external device, and only can really be done so via USB... Unless you opened up your phone yourself and somehow tapped into a different way...
Are you charging you're battery externally? Have you tried a different version of Android? Believe it or not, I've lost USB functionality (software and hardware uses) because of a particular ROM not working well, or even a need for a simple reinstallation...
Unfortunately, rooting your phone comes with risks, and disclaimers are posted for every thread... Not trying to be a jerk... Just saying...
Sent from The Doctor's Nexus 7
didn't I warn you about this...?
Sent from my SGH-T769 using XDA Premium 4 mobile app
Actually, based on what I've read on these forums, as long as I can flash a stock zip via CWM, I should be OK. The man don't care if you install a recovery, they just don't want you to root or install another ROM. I did try other ROMs. In fact I'm now running the rooted stock ROM from one of the forum posts. If I can just get an un-rooted stock zip I'd be home free.
I'm charging externally, switching between the OEM battery and a spare I bought.
And yes I knew the risks, but I'm reasonably sure this is not caused by a ROM, more of a hardware failure.
champ784 said:
Sorry dude... At this point, you've voided your warranty by changing the firmware, and the USB is the only I can think of to revert back to stock... You have to remove your custom recovery with an external device, and only can really be done so via USB... Unless you opened up your phone yourself and somehow tapped into a different way...
Are you charging you're battery externally? Have you tried a different version of Android? Believe it or not, I've lost USB functionality (software and hardware uses) because of a particular ROM not working well, or even a need for a simple reinstallation...
Unfortunately, rooting your phone comes with risks, and disclaimers are posted for every thread... Not trying to be a jerk... Just saying...
Sent from The Doctor's Nexus 7
Click to expand...
Click to collapse