[Q] Galaxy Mini probably bricked... - Samsung Galaxy Mini

Yeah, I probably bricked my Galaxy Mini. Tried to install a custom ROM (The name starts with C, can't remember its name. But it should be pretty popular) by Samsung Recovery Mode by mistake (i blaim my 2 day knowledge at rooting lol). Now it's stuck at boot screen which says "ANDROID" with small white letters. Is there any way to get the stock ROM back? I know Odin can get it working, but for some reason, it won't notice my phone. It was in Download Mode, when I tried to get it working with Odin.
Also, I'm worried if my phone is already bricked; when I'm in Recovery Mode, it says:
--- Appling Muti-CSC --
E:failed to mount /system (Invalid argument)
So it won't recognize /system anymore for some reason.... If someone helps me, I would be very glad, I don't want to use my old Nokia phone forever (no money for new phone, saving for a computer)... It really sucks.

Odin is not recognizing and you flashed c (chocobread) with stock recovery
don't know how it got installed but whatever
have you had your drivers installed
if not then install kies and completely close it (not remove)
open Odin and put files in it
boot phone in download mode
connect the cable
and start flashing
if you are on windows 7 try using windows xp

Darkk1s said:
Yeah, I probably bricked my Galaxy Mini. Tried to install a custom ROM (The name starts with C, can't remember its name. But it should be pretty popular) by Samsung Recovery Mode by mistake (i blaim my 2 day knowledge at rooting lol). Now it's stuck at boot screen which says "ANDROID" with small white letters. Is there any way to get the stock ROM back? I know Odin can get it working, but for some reason, it won't notice my phone. It was in Download Mode, when I tried to get it working with Odin.
Also, I'm worried if my phone is already bricked; when I'm in Recovery Mode, it says:
--- Appling Muti-CSC --
E:failed to mount /system (Invalid argument)
So it won't recognize /system anymore for some reason.... If someone helps me, I would be very glad, I don't want to use my old Nokia phone forever (no money for new phone, saving for a computer)... It really sucks.
Click to expand...
Click to collapse
You would not brick your phone if u accidentally install custom rom from stock recovery, im quite sure bout that cuz i had a friend who did that once with his ace. Just get into download mode, open ODIN, choose the right OPS and flash back to stock again. Erm if it doesn't detect make sure u have the Samsung usb driver installed on your computer. You csee if it's installed from the programs menu in control panel. It's called Samsung usb driver. Then try flashing again. If it doesn't work, try using another cable or a different port.
Sent from my GT-S5570 using xda app-developers app

Darkk1s said:
Yeah, I probably bricked my Galaxy Mini. Tried to install a custom ROM (The name starts with C, can't remember its name. But it should be pretty popular) by Samsung Recovery Mode by mistake (i blaim my 2 day knowledge at rooting lol). Now it's stuck at boot screen which says "ANDROID" with small white letters. Is there any way to get the stock ROM back? I know Odin can get it working, but for some reason, it won't notice my phone. It was in Download Mode, when I tried to get it working with Odin.
Also, I'm worried if my phone is already bricked; when I'm in Recovery Mode, it says:
--- Appling Muti-CSC --
E:failed to mount /system (Invalid argument)
So it won't recognize /system anymore for some reason.... If someone helps me, I would be very glad, I don't want to use my old Nokia phone forever (no money for new phone, saving for a computer)... It really sucks.
Click to expand...
Click to collapse
C = Chocobread
C = CyanogenMod 7, 9, or 10
But i think you flashed CyanogenMod 7.2, in stock recovery ?!
Well, install Samsung USB Drivers, go to download mode, open Odin and then flash a stock ROM. Done.
Next time, learn to flash a Custom Recovery, OK ?

Related

[Q] Can't boot into OS not matter how many times I flash it with Odin...

Hi all I own an international i9000 (Hong Kong version),
My little woe started like this, I was uninstalling RyanZA's OCLF, when I encountered an error where I couldnt uninstall the ext2 tools. I read somewhere on a fix for it, where I downloaded a app called Mount /system (rw / ro) in which i set the system to RW, and then I was able to uninstall ext2 tools.
Afterwards I tried to install the Voodoo lagfix via odin.
After that, it refused to boot to the load screen (Galaxy S logo) and stayed in the i9000 screen saying restore operation then the device reboots itself.
Out of desperation I reflash my phone with my phone's 2.2 firmware "I9000ZSJPE" but that didn't work either, the first time it boots when I flash the firmware, I get taken to recovery mode, and I get this message:
update media please wait
E:Can’t mount /dev/block/stl10
(invalid argument)
E:copy_dbdata_media:can’t mount DBDATA:
your storage not prepared yet,please use UI menu for format and reboot actions.
copy default media content failed
No matter how many times I flash the firmware, I keep getting this message...
Is there any way to get my phone up and running again?
Thanks!
Hey, dont panic, its no biggie... this happened to me last week, you need to find a firmware that contains 'dbdata' im unsure which ones do contain it... i know darkys 9.2 Odin version definately has it... thats the rom i used to fix my phone last week.
EDIT: found this.... this should work :
This one is easy to fix so don't panic.
Download this ROM and extract (Odin 1.7 and 512.pit are included), then do as follows:
-Start Odin and load 512.pit, don't connect the phone yet.
-Make sure "Re-Partition" is checked, don't change anything else.
-Load PDA.tar.md5 as PDA, MODEM.tar.md5 as PHONE and CSC.tar.md5 as CSC.
-Put your Phone on download mode and connect it, start flashing.
When flashing is done, the phone will enter recovery mode, if it get stuck at the same error, simply do a wipe/factory reset and reboot the phone, the phone shall boot normally then.
Link: http://www.multiupload.com/PZNPALHVDW
damn, this is why we NEED XDA forums and other members! I would have hyperventilated if this happened to me! good thing there is a solution posted here
It seems my earlier reply did not send through, but I'll say it again,
Thanks a lot!!! my SGS i9000 is up and running again!!!"
Hey no probs !!! glad to hear you got it fixed nothing worse than the feeling of your beloved precious phone dying infront of your eyes, and the sweat dripping down your forehead when you try mouth to jack input resuscitation.................. or is that just me ??
haha anyways hitting the thanks button would suffice

[Q] A challenging suspected brick case - request for help

Hello Guys
I have a challenging, near brick case.
I have an SGS I9000 I bought from a provider in Singapore. I had a row of misfortune with this device and it was DOA with receiver problem. It was sent twice to Samsung labs and eventually they replaced most of its internals.
When the device eventually returned from the labs it had a 2.1 ROM version of the local provider (IDEA) that was locked for the 3-button maneuver.
I have read all that was written about it, decided to get a decent JIG that work like magic and bring me easily back to DOWNLOAD mode. I decided to install an alternative ROM of my country that had a clear good installation instructions: PilotX 3.0. When this did not work I tired several others, all from ODIN only. In general what happens:
1) After the ODIN restarts the application the ROM goes up and gets stuck after the S opening screen. The device stays black with buttons light on and vibrates every few secs.
2) After the ODIN reset there are messages on the external environment that says E: cant mound /dev/block1st/st110 or 111 (invalid argument)
or: copy dbdata_media cant mound ... copy media content failed
3) I did manage to get to recovery mode despite the errors from the ODIN installation and managed to install from SD card ZIP files the PilotX ROM. It did not give any error messages but it got stuck the eventually the same way.
4) The only ROM I managed to install and actually get running was the local ORANGE ROM. This too did not recognize my SIM and did not solve the 3-button issue.
I am now with a semi bricked device, luckily returning to Download mode easily thanks to the JIG.
Any suggestions guys ?
Thanks
B
You need to flash a full rom in Odin (one with 3 files) and repartition checked. I normally use xxjpc for this purpose.
Sent from my GT-I9000 using XDA App
update
I managed to intall an ACLAIR 2.1 ROM with ODIN that actually works.
I think using a proper PIT did the trick. not sure.
Still:
1) I did get to see that when rebooting there was still a red error message saying something like: "can not access system syn ...."
2) I am still stuck with a phone that refuses to do the 3-button Recovery maneuver.
I guess I am back to square one, searching on the 3-button fix threads for a proper solution. Any good suggestions or boosts. I am after a sleepless night
Thanks

Unable to boot Galaxy Tab

It's a Sprint Galaxy Tab.
I went to the sticky in the dev forum on how to unbrick. Ran Odin and the stock software, it goes through successfully but when I boot it will have the Sprint splash screen and then just goes to a Samsung screen and never comes off of it.
When I go to the Recovery screen, I get this message:
E: Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E: Can't mount CACHE:log/recovery.log
E: Can't open CACHE:log/recovery.log
E: Can't mount /dev/block/mmcblk0p1
(No such file or directory)
it also repeats this when I try to do a wipe on it.
I've tried putting an update.zip on the SD card and it will go about 1/4 of the way before going to the screen with the exclamation point and the Android guy.
I've tried using the EA24 flasher. When I click the Start Download button to start the software update I get an error that says "Unable to open binary file!"
any other ideas on where to go from here?
Sounds like you just need to do a factory reset / wipe in recovery (I saw the same errors and did the same when I flashed the Sprint Gingerbread ROM to my Verizon Tab). That worked for me, I'll bet it works for you too.
EDIT: Hmm, sorry I missed that you said you wiped already?
I used Heimdall to flash kernel + factoryfs.rfs in my case, that alone should be enough to be up and running I would think.
update.zip method is *very* fussy, all files are hash checked, needs stock recovery and stock kernel etc., that did work for me one time, but as I say, it's very fussy. I'd think a stock rooted ROM (like here http://forum.xda-developers.com/showthread.php?t=1161033) may be best. Worth a shot anyway.
yep, did the wipe and it pulled that message.
Tried SuperOneClick to see if I could get anywhere but no luck. Was looking through the sticky about trying to root it and run a different ROM to see if that may help but it looks like I need a working unit to do that to get into some of the settings like USB debugging and what not.
I am going to try the heimdall thing next. Hopefully I can get somewhere with that because I'm running out of options. Appreciate the info!
Make sure you use your shipped stock rom... It maybe you have locked bootloaders and it won't allow you to upgrade without unlocking 1st...
Not sure about the CDMA gtabs though as I use a GSM tab, though reflashing the supplied rom seems to fix most things...
One thing to remember if you get errors in cwm is to go to advanced, then reboot recovery. I have gotten errors just like yours and that fixed them. Also a stock heimdall will fix you. Since we don't mess around with bootloaders on the sgt you gonna be hard pressed to brick you tab. Let me know if this helps.
Personally I've given up on cwm until I see some more progress. Heimdall works well and the stock rooted gb is great for me. I've gotten into a pinch quite a few times lately and come through even gotten the phone...!...pc screen freaked me out esp when I wasn't getting odin to pick the tab up. Let me know if you need some help!
Sent from my SPH-D700 using XDA App

[Q] Potential FULLY bricked Note.

This is my first post, go easy on me! I own a few Android devices, all rooted, and flashed over probably hundreds of times. I know all the risks associated with it, and I take full responsibility for anything that happens to my devices. I've never had any problems in the past getting around recovery and dealing with custom ROMS...nothing that can't be fixed anyway (boot loops, force closes, ect...).
I've never seen so many problems with recovery than I have with the Galaxy Note, however. I mean, if you can't depend on a recovery to work, what are you to depend on? I had a bit of a panic flashing some of the ICS leaks, but all was resolved. No biggie. Everything was running smoothly, and somehow my recovery became fully operational again. I was able to mount /system...and was fully able to flash from CWM again, as opposed to Redpill.
Okay, long winded I know...but here I am. I just flashed angelom's newest kernel with touch recovery. "Cool" I thought. Couldn't hurt. So I went in to do a wipe of /cache and it hung up. No biggie again. I held down the magic three buttons, and when I rebooted back into recovery, I get this....over and over again.
"E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
No files found."
I've tried flashing Redpill again and installing, restoring stock back up, powering down and taking my battery out for a while...bashing my head on the wall. No matter what I do, it doesn't get past the Samsung logo. It was hanging up on booting before, but now it won't even go that far. Do I venture down the path of Odin (which I still am not entirely sure how to use)...or do I have a full brick on my hands? Looks like I might have fried the internal storage. If that's the case, I'm ****ed...simply put.
Anyway, ANY help would be greatly appreciated. Hopefully someone else has run into a similar problem and has a fix...no matter how complicated. Thank you for your time!
Try getting into Download mode (Volume down + Home + Power). If you can do this, then just flash any of the older stock Roms with PC Odin - these are easily rootable using zergrush method - and keep on flashing.
chasmodo said:
Try getting into Download mode (Volume down + Home + Power). If you can do this, then just flash any of the older stock Roms with PC Odin - these are easily rootable using zergrush method - and keep on flashing.
Click to expand...
Click to collapse
I can do that! I was always skeptical of ODIN, but it might be a life saver now.
Okay, so I get the little green Android guy and it says "Downloading...Do not turn off target!" So then I download PC Odin, connect USB cable and flash away? Sounds simple enough. I'd really hate to think I have a 700 dollar paperweight. I'll do some homework first. Thank you, by the way!
smalmagal said:
Okay, so I get the little green Android guy and it says "Downloading...Do not turn off target!" So then I download PC Odin, connect USB cable and flash away? Sounds simple enough. I'd really hate to think I have a 700 dollar paperweight. I'll do some homework first. Thank you, by the way!
Click to expand...
Click to collapse
Yes. Go here, download N7000XXKK9 stock Rom and flash it with PC Odin.
Then go here, and root it using Method 2: Root + CWM recovery.
I use Linux, so I'll have to wait to use my friends Windows PC. Installing a virtual box is more trouble than anything. This is how I rooted my device the first time. They don't make things simple for us Linux users! Anyway, I'll let you know how it goes tomorrow. Thanks again!
chasmodo said:
Yes. Go here, download N7000XXKK9 stock Rom and flash it with PC Odin.
Then go here, and root it using Method 2: Root + CWM recovery.
Click to expand...
Click to collapse
Edited: Sometimes after flashing stock Rom you get into bootloop when Odin restarts the phone. Don't panic if this happens. Pull out your battery, wait a bit, put it back, boot into stock Recovery (Volume up + Home + Power), and do factory reset and cache wipe. Reboot and enjoy.
I got the same thing tonight!!! Damn!
I can't do anything with /data partition in any version of CWM - RedPill too. It just hangs. It can't be wiped or formatted. And phone doesn't boot. I flashed KKA 1 file firmware via odin, but the phone still doesn't boot. I'm now downloading KK9 in hope that it is 3 file (because I can't find info whether it is 1 or 3 file) to try to flash it. Also using pit and repartition could fix it, but I am frightened by messages "do not ever tick repartition or you get brick".
Very sad.
guys, i need help please. My Note not work in download mode and cwm recovery. I made a homemade JIG, but not works, too. I tested the homemade JIG in a galaxy ace and in a galaxy S2 and enter instantly in download mode but in galaxy note no. my pc and other pc does not recognize the phone either. Can I do anything?
Thanks
eliot_11 said:
guys, i need help please. My Note not work in download mode and cwm recovery. I made a homemade JIG, but not works, too. I tested the homemade JIG in a galaxy ace and in a galaxy S2 and enter instantly in download mode but in galaxy note no. my pc and other pc does not recognize the phone either. Can I do anything?
Thanks
Click to expand...
Click to collapse
plug phone into usb to pc. Take battery out, wait 30 sec, while holding volume down put battery in and keep holding until download screen comes up
see if this helps
or do this if that doesn't help
http://forum.xda-developers.com/showpost.php?p=13856913&postcount=5
B.Maximenko said:
I got the same thing tonight!!! Damn!
I can't do anything with /data partition in any version of CWM - RedPill too. It just hangs. It can't be wiped or formatted. And phone doesn't boot. I flashed KKA 1 file firmware via odin, but the phone still doesn't boot. I'm now downloading KK9 in hope that it is 3 file (because I can't find info whether it is 1 or 3 file) to try to flash it. Also using pit and repartition could fix it, but I am frightened by messages "do not ever tick repartition or you get brick".
Very sad.
Click to expand...
Click to collapse
Yup...exactly...my /cache partition seems fine now...but it's hanging on /data too! Did you flash the new touch kernel from angelom too? I don't want to point fingers, but I would at least like to know what the "root" cause is. Anyway, instead of using ODIN, I used Heimdall. I'm at pretty much the same place I was before, except now I have Samsung's recovery....
Anyway, I'll keep flashing different firmwares, and I'll see where we get.
Edit: I used a .pit file as well. Was I not supposed to do that? I don't think it did any harm, as my phone still turns on!
eliot_11 said:
guys, i need help please. My Note not work in download mode and cwm recovery. I made a homemade JIG, but not works, too. I tested the homemade JIG in a galaxy ace and in a galaxy S2 and enter instantly in download mode but in galaxy note no. my pc and other pc does not recognize the phone either. Can I do anything?
Thanks
Click to expand...
Click to collapse
see my signature
Okay, so I have an idea. I flashed the repack kernel and got CWM back...but obviously my /data partition is still ****ed. Would it be possible to do a repartition of it? Do I need an ICS pit file to do this?...because I noticed the Chainfire repack has a data.img, and I tried flashing it using a GB .pit file, and it hung up...so, I think this might be my last hope!
Hey I also flashed the new ICS kernel posted by angelom...
And having same problem....
getting errors like this while entering CWM
E:can't mount/cache/recovery/command
E:can't mount/cache/recovery/log
E:can't open/cache/recovery/log
E:can't mount/cache/recovery/last_log
E:can't open/cache/recovery/last_log
Okay, so I feel a little better that it's not just me! Obviously no one, including the developer, is to blame...but the kernel is definitely the cause, and I'm having trouble with the fact that I might be spending 650 on another phone, just for the simple fact that I thought it would be intuitive to have a touch recovery. Grrrrrrr.....
thanks for your help, but my note not have signals of life. Thanks
eliot_11 said:
thanks for your help, but my note not have signals of life. Thanks
Click to expand...
Click to collapse
Sorry to hear that elliot. Is it under warranty/ensured?
Sent from my GT-N7000 using Tapatalk
I went in to wipe /cache as well, and that's when it all happened. I don't have a complete brick, but it might as well be. If I can get into recovery and download mode, but nothing works, then what good is it? A constat bootlooping phone is no phone at all. I don't insurance, and as far as I can tell my warranty is void. So I think my best option would be to send the phone directly to Samsung and see what they can do. It's better than nothing.
smalmagal said:
Yup...exactly...my /cache partition seems fine now...but it's hanging on /data too! Did you flash the new touch kernel from angelom too? I don't want to point fingers, but I would at least like to know what the "root" cause is.
Click to expand...
Click to collapse
Yes, it happened right after I flashed angelom 1.1. I used ver 1.0 for some time, didn't try to wipe data, but rom was running OK. Then I flashed imilka's v0.3 and angelom 1.1 on top, tried to wipe data and got that error message. After that, my phone hangs on boot logo and can't do anything with /data partition, and I can't restore any of my backups - it says error in /data. I flashed stock KKA firmware with odin, it didn't fix /data - stock recovery also can't wipe it.
Samsung galaxy note completely dead !!
my rooted galaxy note was on rocket rom which i updated to ics theme, and without rebooting i flashed the zip file to reset binary data count.
all this was happening in cwm.
then i opted to reboot to system and my galaxy note never rebooted.
what to do? where do i go?
phone s rooted but wont go into cwm mode, nor into flashing mode,,, does not even charge...
smalmagal said:
This is my first post, go easy on me! I own a few Android devices, all rooted, and flashed over probably hundreds of times. I know all the risks associated with it, and I take full responsibility for anything that happens to my devices. I've never had any problems in the past getting around recovery and dealing with custom ROMS...nothing that can't be fixed anyway (boot loops, force closes, ect...).
I've never seen so many problems with recovery than I have with the Galaxy Note, however. I mean, if you can't depend on a recovery to work, what are you to depend on? I had a bit of a panic flashing some of the ICS leaks, but all was resolved. No biggie. Everything was running smoothly, and somehow my recovery became fully operational again. I was able to mount /system...and was fully able to flash from CWM again, as opposed to Redpill.
Okay, long winded I know...but here I am. I just flashed angelom's newest kernel with touch recovery. "Cool" I thought. Couldn't hurt. So I went in to do a wipe of /cache and it hung up. No biggie again. I held down the magic three buttons, and when I rebooted back into recovery, I get this....over and over again.
"E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
No files found."
I've tried flashing Redpill again and installing, restoring stock back up, powering down and taking my battery out for a while...bashing my head on the wall. No matter what I do, it doesn't get past the Samsung logo. It was hanging up on booting before, but now it won't even go that far. Do I venture down the path of Odin (which I still am not entirely sure how to use)...or do I have a full brick on my hands? Looks like I might have fried the internal storage. If that's the case, I'm ****ed...simply put.
Anyway, ANY help would be greatly appreciated. Hopefully someone else has run into a similar problem and has a fix...no matter how complicated. Thank you for your time!
Click to expand...
Click to collapse
sometimes it doesnt recover, i had it with the hd2 aswell, it isnt a note specific issue, as for the title, it is misleading, a brick is not being able to turn the phone on, seeing as you coudl where did you get the notion it was bricked?
the errors in the recovery are standard if no rom is installed

[Q] tried to install TWRP on galaxy ace now wont boot

Hey. Im not sure if there is a thread similar to this or not, I tried looking around and cant see any. The one i did see, was for a tablet.
Here goes....
I have a Samsung Galaxy Ace S5830i. It has gingerbread on. I rooted it 2 days ago as eventually I want to install JB onto it. I Tried to install TWRP (TWRP-2.4.1.0-cooper) onto my device, then rebooted after a 'successful' install. Only when I reboot, even now, it doesnt boot up. It gets to the Samsung screen, then stays there. Left it all night ( 12 hours or so ) and checked this morning, still the same.
HERE IS HOW I DID IT:
1. Rebooted into Recovery ( by holding Volume Up + Home + Power )
2. Apply update from sdcard
3. Scrolled to the file (TWRP-2.4.1.0-cooper)
4. Said successfully installed and rebooted.
I then swapped SD Card with another phone so i could remove this file of the Samsung phone, and replace with with recovery-clockwork-5.0.2.6-galaxyace-fix then put the SD Card back into samsung.
SOOO, today I tried the same procedure, but with another custom recovery (recovery-clockwork-5.0.2.6-galaxyace-fix) and now I get this messages:
E:Error in /tmp/sideload/package.zip
I have even used ODIN, and tried to flash that way, BUT IT SAYS MY PHONE IS NOT CONNECTED.
All I want to do now is be able to boot, NORMALLY so i can access my phone again. My phone is on contract, so I cant send it back as it has been rooted.
PLEASE HELP.
thanks in advance.
P.S ON THE ACTUAL RECOVERY PAGE, I GET THIS ERROR MESSAGE:
E:failed to mount /system (Invalid argument)
AW: [Q] tried to install TWRP on galaxy ace now wont boot
Dont think those recoveries are for s5830i
Theyre for the s5830.
Correct me if im wrong
Sent from my GT-S5830 using xda app-developers app
回覆: [Q] tried to install TWRP on galaxy ace now wont boot
s5830i....lol....hard brick....I'm feeling sry for u
Btw wrong section
從我使用 Tapatalk 2 的 GT-S5830 發送
If u can enter download or recovery mode..then your device is not hard bricked..
And u own a cooper-ve(Galaxy Ace i 5830) then u flashing wrong recovery ..
Go to Galaxy Ace i 5830 development and install a suitable recovery..n then proceed..
Stopped reading after I read the first para
Your device is completely f-ed up and there is no way of recovering it except for service center/jtag

Categories

Resources