Database Develop

Help Me.

Nothing found using search.
I cant get into [Home+Power] stays at G1 screen. Other then that it does power up and go into phone. and [Power+Camera] works. Any help how to fix this ?

you probably need to reflash your recovery image. the thing that sucks is that the recovery image links are down so if you don't have a copy of it, well you can imagine....

Can you give me a link to one ? And tell me how to reflash ?
And BTW , you seem to always be there , big thanks man.

yeah, seems like you'll need to reflash the recovery.
I actually have a saved copy of the 1.4 recovery, if you give me your email i can send to you. the instructions to install it are on the original thread, here.

TheUriel said:
Can you give me a link to one ? And tell me how to reflash ?
And BTW , you seem to always be there , big thanks man.
Click to expand...
Click to collapse
Dude google it, it's like, the 4th link down, i'd post the URL but it took me 5 seconds to find it, so I'll leave it to you.

A question ?
For the past 1hrs ive been trying to get my phone to work. I installed cynogens recovery image 1.4 and after that tryed installing a theme and got a black screen i then notice it was because i didnt remove the icons b4 this. I was stuck cause i didnt have an sdcard reader so ive been using my cousin LG phone to transfer my data to the sdcard. So i tryed re-flashing the rom (Cynogen 4.0.4) with wip. Still got the black screen. Tryed a new rom (JACxHEROSki-v2.1) with wip , goes pass the G1 screen to the aqua blue cynogen android scate board screen to the black screen. Help ?
MOD EDIT
if you have a ? please give a hint in the title to what it is.
thank you

TheUriel said:
For the past 1hrs ive been trying to get my phone to work. I installed cynogens recovery image 1.4 and after that tryed installing a theme and got a black screen i then notice it was because i didnt remove the icons b4 this. I was stuck cause i didnt have an sdcard reader so ive been using my cousin LG phone to transfer my data to the sdcard. So i tryed re-flashing the rom (Cynogen 4.0.4) with wip. Still got the black screen. Tryed a new rom (JACxHEROSki-v2.1) with wip , goes pass the G1 screen to the aqua blue cynogen android scate board screen to the black screen. Help ?
Click to expand...
Click to collapse
you might want to avoid constantly opening new threads, especially one that just has "?" in the subject; this one might get closed.
if your sdcard is partitioned correctly for cyanogenmod (ext2/ext3 - fat32) then you'll probably need to wipe the ext2/ext3 partition and wipe then reflash the rom. I haven't gone to a HERO rom yes myself, so i'm not sure if there is another step involved for that.

DavidChill said:
you might want to avoid constantly opening new threads, especially one that just has "?" in the subject; this one might get closed.
if your sdcard is partitioned correctly for cyanogenmod (ext2/ext3 - fat32) then you'll probably need to wipe the ext2/ext3 partition and wipe then reflash the rom. I haven't gone to a HERO rom yes myself, so i'm not sure if there is another step involved for that.
Click to expand...
Click to collapse
Ive never partitioned for Cynogen i have a clean 1g no partitions. Its always worked for me.

Im assuming that you didnt create a nandroid backup when you installed the recovery image? and let's both assume since you had Cyan running before that you have the correct Radio and SPL images.
ok, if you have no partitions we can skip a couple of steps.. try this, connect your phone to youe PC, boot into recovery with Home & Power and type the following commands.
alt&X to enter console
push enter
ums_enable
this will mount your sd and open it on your PC so you can verify that you have the correct update.zip on the root of your SD.
ums_disable
reboot recovery
alt&W
alt&S
If you are going to start flashing roms you really want to consider getting a bigger SD card, my nandroid backup is like, 900mb and without that it's kinda like playing russian roulette with your phone. I hope this helps.

ironnius said:
Im assuming that you didnt create a nandroid backup when you installed the recovery image? and let's both assume since you had Cyan running before that you have the correct Radio and SPL images.
ok, if you have no partitions we can skip a couple of steps.. try this, connect your phone to youe PC, boot into recovery with Home & Power and type the following commands.
alt&X to enter console
push enter
ums_enable
this will mount your sd and open it on your PC so you can verify that you have the correct update.zip on the root of your SD.
ums_disable
reboot recovery
alt&W
alt&S
If you are going to start flashing roms you really want to consider getting a bigger SD card, my nandroid backup is like, 900mb and without that it's kinda like playing russian roulette with your phone. I hope this helps.
Click to expand...
Click to collapse
Sorry , and everything you told me worked great. Thanks man.

FYI Start stating a short clip of your issue in the title of the thread.
Most likely if you don't, either:
A: your thread will be locked, or
B: you will not have as many fellow members trying to help you out.
TRhink of it this way, people here are busy.....they would like to know what they are gonna head into prior too opening a thread

ironnius said:
Im assuming that you didnt create a nandroid backup when you installed the recovery image? and let's both assume since you had Cyan running before that you have the correct Radio and SPL images.
ok, if you have no partitions we can skip a couple of steps.. try this, connect your phone to youe PC, boot into recovery with Home & Power and type the following commands.
alt&X to enter console
push enter
ums_enable
this will mount your sd and open it on your PC so you can verify that you have the correct update.zip on the root of your SD.
ums_disable
reboot recovery
alt&W
alt&S
If you are going to start flashing roms you really want to consider getting a bigger SD card, my nandroid backup is like, 900mb and without that it's kinda like playing russian roulette with your phone. I hope this helps.
Click to expand...
Click to collapse
You can go in the nandroid folder and delete old backups, folder names have dates. You can also store all of the folders and put them on your sdcard as needed, Nandroid only uses the one with the newest date anyways.

TheUriel said:
Sorry , and everything you told me worked great. Thanks man.
Click to expand...
Click to collapse
Hey no problem, I'm glad things worked out for you.

[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

I Invented a whole New Level of Fail

So I'm in CWM about to install a new ICS rom. I go to mounts and storage and start formatting everything. As I finish with that, I start trying to make my way to the "mount usb storage" option to I can copy the .zip files from my computer.
However, I accidentally mount or unmount one of the folders near the top. I'm not sure which one (I was a little distracted by something else at the time). So I figure why not just reboot into recovery (in hindsight, bad idea).
Now the phone is stuck at the AT&T Logo. I'm not sure its a "bootloop" since it always stays at the white screen and never goes into black.
I've tried every button combo I can think of to get back into recovery or download mode, but no luck.
Any ideas?

Just flash with ODIN. Use a JIG

Well you can try
Open ODIN
take out battery
connect phone to computer insert battery while holding Vol up+vol down (assuming on i897 bootloaders)
flash to stock
OR
Jig
... I typed to slow.... lol

And I made mine short and too the point for people that don't read

Hangampalli said:
So I'm in CWM about to install a new ICS rom. I go to mounts and storage and start formatting everything. As I finish with that, I start trying to make my way to the "mount usb storage" option to I can copy the .zip files from my computer.
However, I accidentally mount or unmount one of the folders near the top. I'm not sure which one (I was a little distracted by something else at the time). So I figure why not just reboot into recovery (in hindsight, bad idea).
Now the phone is stuck at the AT&T Logo. I'm not sure its a "bootloop" since it always stays at the white screen and never goes into black.
I've tried every button combo I can think of to get back into recovery or download mode, but no luck.
Any ideas?
Click to expand...
Click to collapse
it happened with me also no need to use USB jig just connect your device to computer in download mode then flash any Odin one click package with boot loader
bootloader is necessary as you just wiped boot from recovery

If he wiped his bootloader it would be hard bricked. I would attempt it without bootloader first.
Sent from my ICS powered Captivate using Tapatalk

prbassplayer said:
If he wiped his bootloader it would be hard bricked. I would attempt it without bootloader first.
Sent from my ICS powered Captivate using Tapatalk
Click to expand...
Click to collapse
there are 2 types of boot loader one for going to dload and recovery mode and one for booting phone he removed the bootloader which boot phone and if it is not boot loader then can u please tell what is exactly the boot in mount and storage option

cwm wont let you wipe your bootloader or efs. he should be fine if he reads...
there is NO INSTRUCTIONS ANYWHERE that say to wipe everything in that menu.
if anything system and data (factory reset).
odin flash to stock.

dhlalit11 said:
there are 2 types of boot loader one for going to dload and recovery mode and one for booting phone he removed the bootloader which boot phone and if it is not boot loader then can u please tell what is exactly the boot in mount and storage option
Click to expand...
Click to collapse
that is just wrong in so many ways. simply put if bootloaders were dammaged/missing the phone would not turn on.

TRusselo said:
that is just wrong in so many ways. simply put if bootloaders were dammaged/missing the phone would not turn on.
Click to expand...
Click to collapse
OK I just want to know only for knowledge that what is that boot option in mount and storage so I can give exact info to others

there is no bootloader option in mounts and storage...
looking at it now the options are to mount or format:
system
cache
datadata
sdcard
data
emmc
no boot or bootloader.

TRusselo said:
that is just wrong in so many ways. simply put if bootloaders were dammaged/missing the phone would not turn on.
Click to expand...
Click to collapse
if removing primary boot loader will not let the phone to show anything then why there are two boot loader just think
---------- Post added at 10:37 PM ---------- Previous post was at 10:28 PM ----------
TRusselo said:
there is no bootloader option in mounts and storage...
looking at it now the options are to mount or format:
system
cache
datadata
sdcard
data
emmc
no boot or bootloader.
Click to expand...
Click to collapse
I am using glitch kernel which have cwm v5.5 installed and the first format option the mount and storage is of boot just go to recovery and see it
do not give people wrong info just for making yourself true

dhlalit11 said:
if removing primary boot loader will not let the phone to show anything then why there are two boot loader just think
Click to expand...
Click to collapse
Yes there is a primary and secondary bootloader but if 1 is broken, gone the phone won't BOOT at all (hard bricked). FYI secondary bootloader handles the key combos. Im not saying he doesn't need to flash bootloaders BUT I would try to odin without bootloaders first see if it works. Less chance of killing your phone.

TRusselo said:
there is no bootloader option in mounts and storage...
looking at it now the options are to mount or format:
system
cache
datadata
sdcard
data
emmc
no boot or bootloader.
Click to expand...
Click to collapse
I am using glitch kernel which have cwm v5.5 installed and the first format option the mount and storage is of boot just go to recovery and see it
do not give people wrong info just for making yourself true

prbassplayer said:
Well you can try
Open ODIN
take out battery
connect phone to computer insert battery while holding Vol up+vol down (assuming on i897 bootloaders)
flash to stock
OR
Jig
... I typed to slow.... lol
Click to expand...
Click to collapse
Thanks, I'm in download mode now.

prbassplayer said:
Yes there is a primary and secondary bootloader but if 1 is broken, gone the phone won't BOOT at all (hard bricked). FYI secondary bootloader handles the key combos. Im not saying he doesn't need to flash bootloaders BUT I would try to odin without bootloaders first see if it works. Less chance of killing your phone.
Click to expand...
Click to collapse
I firstly downloaded a gb firmware with bl but due to slow connection I was not able to download that firmware without bl and since then am flashing that fw with bl without any problem I have flashed that few 10 times

dhlalit11 said:
I firstly downloaded a gb firmware with bl but due to slow connection I was not able to download that firmware without bl and since then am flashing that fw with bl without any problem I have flashed that few 10 times
Click to expand...
Click to collapse
Good for you. But if the user has a less than stable cable or God knows what else your advice will lead to a brick for something that could have been fixed with out a bl package. Btw it's not smart attacking a rom dev on the forums.... just saying.

dhlalit11 said:
I am using glitch kernel which have cwm v5.5 installed and the first format option the mount and storage is of boot just go to recovery and see it
do not give people wrong info just for making yourself true
Click to expand...
Click to collapse
glitch kernel does, I AM SOOO SORRY, my other phone doesn't run glitch.
and take your own advice as well. how do you know it formats bootloader?
do you know what would happen if you formatted bootloader?
and try to understand not everyone sees the exact same thing you do unless we know what kernel you are using.

OK lets get the kernel tester for Glitch in this conversation. Wiping boot.img in CWM wipes the kernel because on MTD ROM's. The kernel is contained in a boot.img, not a zImage.... So no the only program or recovery system that has access to the bootloaders is ODIN or HEIMDALL. CWM recovery doesn't even have access to bootloaders on any other phone either... So TRusselo is completely right and dhlalit11 is wrong...

S-nap B-eock
a recovery that wipes its own bootloader would just be retarded.

[Q] Optimus black bootloop

hello!
i'm quite new here and i would gladly appreciate if anybody could redirect me to an existing thread (if any) regarding my concern.
i have my phone installed with rom manager via google play.i made a rom backup as recommended before downloading the recommended cyanogenmod version for my phone. i followed all the instruction about the rom, devlik, cache etc. everything was going well, when suddenly during clockworkmode (forgive my spelling), my phone booted and i thought it successfully installed. but then i noticed that it was booting was continuous even after 10 mins and more. i panicked and i removed the battery. and then i tried the lg shortcut for recovery (i think) which then appear. i chose to restore backup and then reboot. but nothing happened. it still "booting". everytime i power on my phone, it only show the lg logo and the blinking shortcuts. i tried to vol+/- and power but to no avail. i cant go back to the recovery panel. what should i do? :'(
i would kindly appreciate any help you could extend to me.
thank you in advance!

Hello mitzibelle,
Looks like your backup is no good also....
Did you press any keys during the backup procedure? Because backup will stop and not finish if that happened resulting in a unfinished & unusable backup.
What you can do is download the rom you want to install again, to make sure the file is ok check the md5.
Copy this file to your sd card, reboot into recovery and choose install from sd. Browse to the zip file and install.
This should result in a working phone.
Let me know if it was useful or not.
Sent from my LG-P970 using xda premium

Duumke1 said:
Hello mitzibelle,
Looks like your backup is no good also....
Did you press any keys during the backup procedure? Because backup will stop and not finish if that happened resulting in a unfinished & unusable backup.
What you can do is download the rom you want to install again, to make sure the file is ok check the md5.
Copy this file to your sd card, reboot into recovery and choose install from sd. Browse to the zip file and install.
This should result in a working phone.
Let me know if it was useful or not.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
I can't seem to reboot my phone into recovery because the volume+/- and power button combination has no effect. if i put a new rom in the sd card and placed in again in the phone, will the hardware buttons work again? is having a "defective" backup rom affecting the recovery button shortcut or is it a different problem?
thank you for your help

You should be able to enter clockworkmod recovery by pressing the G button below the volume buttons. As soon as the 4 buttons staft to flash. Or just turn it off and on again and start bashing the G key immediately.
As soon as you enter cmw you might also try to flash your previously downloaded file again. Worked for me a few times.
A defective backup does not have any influence on the hardware buttons, also placing a downloaded rom on the sd would not affect the buttons.
Don't forget to clear the caches before you install your downloaded rom if it's different then the one you used when the phone was still working..... Maybe it's wise to clean the caches anyways concerning your previous problems. Wipe factory, cache & dalvik cache also. Dalvik cache can be found under the advanced menu option.
Hope this is useful
Sent from my LG-P970 using xda premium

If you can't go into recovery you have to do emergency recovery with Smart Flash Tool.
Pressing the G-key repeatedly on boot to go into recovery is only if it has Huexxs G-recovery.

xonar_ said:
If you can't go into recovery you have to do emergency recovery with Smart Flash Tool.
Pressing the G-key repeatedly on boot to go into recovery is only if it has Huexxs G-recovery.
Click to expand...
Click to collapse
I thought it was a cmw 5.8x feature.
Sorry for that.....
Sent from my LG-P970 using xda premium
---------- Post added at 06:49 PM ---------- Previous post was at 06:45 PM ----------
But how is it possible that I can access it with a stock rooted rom? Is everyone using his g-recovery script?
Sent from my LG-P970 using xda premium

thank you for your replies. i will try to do emergency recovery. i have an existing smartflash tool at home with the .bin/.fls files i've used when i flash my phone before. would this suffice? or i need to download a new one/version? I will try this tutorial link: http://forum.xda-developers.com/showthread.php?t=1448803 and hope that i can get to the s/w upgrade screen. will give you feedback after.

mitzibelle said:
thank you for your replies. i will try to do emergency recovery. i have an existing smartflash tool at home with the .bin/.fls files i've used when i flash my phone before. would this suffice? or i need to download a new one/version? I will try this tutorial link: http://forum.xda-developers.com/showthread.php?t=1448803 and hope that i can get to the s/w upgrade screen. will give you feedback after.
Click to expand...
Click to collapse
That will work
Sent from my LG-P970 using Tapatalk 2

hi there!
i just did the instructions in the link, and it works!
I have to flash it twice because i forget to clear cache, delvik, and restore factory setting.
i hope my battery would not die very quickly (i usually have a battery life of 12 hours on standby with minimal texting) and hope to not encounter any probs in the next few days.
thanks!:victory:

[Q] whats this? i9001 bricked, damaged partition? cant wipe data, do factory reset.

Hi people,
i dont know where to go! i have read dozen of sites and post... am i right here?
my S+ i9001
PDA i9001xxkq7
Phone: i9001xxkpk
csc i9001dbtkp2
can:
boot in download mode
can boot recovery mode
can be flashed via odin
can NOT:
-boot to system (always hang or freeeze or shuts down when Samsung logo comes)
-data can not be wiped (Processbar starts but never really start doing something) CWM6. I had some other recoverys and they gave me some messages like can not accsess data/csc or something like these messages in other posts.
-can not do anything in recoverymode exepted, wipe cache.
-can not update zip
-can not gain accsess to sdcard ore sideby
-cant reboot in recovery.
i flashed with odin (and Aries.ops):
-broodROM_RC5
-the right StockROM
-phone seems to be bricked
-no access with Quickflash (dont know if debug mode was or is enabled)
i found some people with similar problems with other devices (i9000 // i9100), but not with the i9001. so i write it here.
always the answer was try a full wipe/reset, but i cant or dont know how to it when the recoverymod or stock recovery doesnt do it.
kind regards
Daniel
im Stuck! where do i have to start further steps?

incredibledan said:
Hi people,
i dont know where to go! i have read dozen of sites and post... am i right here?
my S+ i9001
PDA i9001xxkq7
Phone: i9001xxkpk
csc i9001dbtkp2
can:
boot in download mode
can boot recovery mode
can be flashed via odin
can NOT:
-boot to system (always hang or freeeze or shuts down when Samsung logo comes)
-data can not be wiped (Processbar starts but never really start doing something) CWM6. I had some other recoverys and they gave me some messages like can not accsess data/csc or something like these messages in other posts.
-can not do anything in recoverymode exepted, wipe cache.
-can not update zip
-can not gain accsess to sdcard ore sideby
-cant reboot in recovery.
i flashed with odin (and Aries.ops):
-broodROM_RC5
-the right StockROM
-phone seems to be bricked
-no access with Quickflash (dont know if debug mode was or is enabled)
i found some people with similar problems with other devices (i9000 // i9100), but not with the i9001. so i write it here.
always the answer was try a full wipe/reset, but i cant or dont know how to it when the recoverymod or stock recovery doesnt do it.
kind regards
Daniel
im Stuck! where do i have to start further steps?
Click to expand...
Click to collapse
+1
---------- Post added at 03:48 PM ---------- Previous post was at 03:03 PM ----------
The Same problem with my phone!!
I tried every thing every cwm recoveries and root stock rom and broodrom no boot
Please somebody can help us?
Thank you

I9001 cant format data and emmc
Update,
i finally got an CWM running! aktually 5.5.0.4 but the 6.0.1 and 6.0.2 alsoworked at the end.
now all i cant do is, formatting data and/or mount/format emmc.
Plugged in via USB Cable to PC i can access (internal) sdcard and copy all zips i want. I also cann install them, but i cant wipe data.
i geuss there is an hardware issue, so that all these fine mods are biting on stone, trying to format the "partition"
This results in unbootable systems..i think
At least i tried cm-9-20130220-EXPERIMENTAL-ariesve-rc5 with kernel 3.00, no luck.
i this hardbricked? damaged? i geuss im close to the final. but wich one.....
last try is this hint :http://forum.xda-developers.com/showthread.php?t=2173180
but ODIN crashes when trying the MD5 checksum
thanks for reading!
dan

...
tried to reduce the i9001reset.tar.md5 file with repacking it without the cache and system file. but the reset.zip still has 750mb and odin crashes checking the md5.
are there any other methods to check if the data partition or the emmc.ic is damaged? i cant format via CWM or stock recovery, results in endless process...
and Quickflasher also crashed trying to "wipe at start" mmcblk0p17 (data)
greetz from Berlin
Dan

samen problem
I got the samen problem, please some help. (10 hours working on it
I dit odin to stock
odin to recovery 6
formated sd
installed roms
nothing works, cant mount, cant wipe date,
Has it to do something with .ext (i dunno this really and dunno how to change

did you try to wipe data from stock recovery after install stock rom?
Sent from my GT-I9001 using xda app-developers app

danger
ATTENTION dont try the reset.zip partition recovery as described above! It has killed my phone! i lost any lifesigns from the device, no vital functions over the battery or powersupply. i just cant switch it on again.
this is my end with this!

macar said:
did you try to wipe data from stock recovery after install stock rom?
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
yes, i tried but it did not work, neither from stock or custom ROM.

I'm having the exact same problems. It all started when I updated CWM to 6.0.2.8 as recomended by ivendor, in order to flash CM10. Since then I can't wipe data partition, and no matter what I flash (through both Odin and CWM), the phone doesn't boot anymore. Tried to restore original Samsung ROM, no success... Hasn't anyone figure it out? It seems a large number of user have dealt with this issue in the last days, perhaps the coder of CWM 6.0.2.8 should explain how to fix this mess.
I went to a local phone service, and they said they can't do anything, the whole internal memory has to be replaced. I can't believe this.

No solution?
I have exectly the same problem and i tried everything. I still can get to recovery and download mode, because i didnt mess with reseting broken partition. Can this be solved? I didnt find anyhing in threads, and it seems that a lot of people have this kind of problem now. It all happend on my s+ while i was trying to flash CM10 Beta4.

repair in warranty
Ledo13 said:
I have exectly the same problem and i tried everything. I still can get to recovery and download mode, because i didnt mess with reseting broken partition. Can this be solved? I didnt find anyhing in threads, and it seems that a lot of people have this kind of problem now. It all happend on my s+ while i was trying to flash CM10 Beta4.
Click to expand...
Click to collapse
OK Guys,
here im back. After killing the phone i called samsung i (i was still in warranty), an then i send it to an repair center of their choice. it tooks two weeks an here i got it back. dont know what they have done. but it didnt cost me anything.
end of story from me
greetz dan

search for emmc bug thread in development section http://forum.xda-developers.com/showthread.php?t=2224029
the recovery you have used was compiled over a 3.0 kernel, it has a bug that brick phones, like the galaxy s2 and galaxy note.

New motherboard
incredibledan said:
OK Guys,
here im back. After killing the phone i called samsung i (i was still in warranty), an then i send it to an repair center of their choice. it tooks two weeks an here i got it back. dont know what they have done. but it didnt cost me anything.
end of story from me
greetz dan
Click to expand...
Click to collapse
I got my phone back from service in a 4 days and they changed my motherboard. Now I have completely new motherboard (plus I didnt pay a thing because I still got warranty). Obviously they didn't find out whats wrong with my phone so they put new motherboard

Ledo13 said:
I got my phone back from service in a 4 days and they changed my motherboard. Now I have completely new motherboard (plus I didnt pay a thing because I still got warranty). Obviously they didn't find out whats wrong with my phone so they put new motherboard
Click to expand...
Click to collapse
I managed to "rescue" my eMMC-bricked phone by doing everything I could find about the eMMC brick bug killed my i9001. No root but I can live with that until someone comes up with a better fix.. Good luck, I wish I had a better step by step instruction list on how I did it but honestly I just frantically tried things over and over in different order and finally got it going.
http://forum.xda-developers.com/showthread.php?t=2234489
I guess...
1. Get TWRP 2.2.2.1 or CWM 5.5.0.4/the new 2.6-based 6.0.2.8 CWM recovery flashed.
2. Use QuickWipe (link in my post to the OP).
3. Use ODIN 4.43 to flash that 1.4GB fixmev2.tar file (I did it at least 2-3 times during different stages)
4. Follow the instructions in the links in my post.
5. Good luck.
6. Wait for the devs to solve this problem permanently with new kernels and ROMs and thank them when they solve it.

Scyphe said:
I managed to "rescue" my eMMC-bricked phone by doing everything I could find about the eMMC brick bug killed my i9001. No root but I can live with that until someone comes up with a better fix.. Good luck, I wish I had a better step by step instruction list on how I did it but honestly I just frantically tried things over and over in different order and finally got it going.
http://forum.xda-developers.com/showthread.php?t=2234489
I guess...
1. Get TWRP 2.2.2.1 or CWM 5.5.0.4/the new 2.6-based 6.0.2.8 CWM recovery flashed.
2. Use QuickWipe (link in my post to the OP).
3. Use ODIN 4.43 to flash that 1.4GB fixmev2.tar file (I did it at least 2-3 times during different stages)
4. Follow the instructions in the links in my post.
5. Good luck.
6. Wait for the devs to solve this problem permanently with new kernels and ROMs and thank them when they solve it.
Click to expand...
Click to collapse
EDIT: after it died last night (tried to force root permissions and it would no longer boot) and fiddling to get it back to working condition I tried flashing the file in this post (http://forum.xda-developers.com/showpost.php?p=38671295&postcount=2) to reset partitions and the phone is now stone dead... a true brick.. absolutely nothing happens when I try to power up, enter recovery mode, whatever.. it's dead... stone cold..