Hi,
first post here.
Hopefully someone here can help me.
I was trying to flash a JB Rom, when I landed myself in a boot loop.
Now, my predicament is, I do not have the ability to get into recovery or download mode with the button combination.
I am on a Mac, if that adds anything relevant. Right now, my phone is unusable.
Can anyone help?
Thanks very much
Sacha
sanosoke said:
Right now, my phone is unusable.
Can anyone help? Thanks very much
Sacha
Click to expand...
Click to collapse
Ok, First remove battery, press power for a min, remove EXT SD card and SIM card and reinsert battery and try for download mode ( you must know how to, if not find out use SGS WIKI here http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Series
what are you using on MAC to flash?
xsenman said:
Ok, First remove battery, press power for a min, remove EXT SD card and SIM card and reinsert battery and try for download mode ( you must know how to, if not find out use SGS WIKI here http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Series
what are you using on MAC to flash?
Click to expand...
Click to collapse
Thanks xsenman, removing those two things seemed to work! Took me into recovery at least, still seeing if I can make something boot up now.
I use a mac, but I flash just straight on the phone. I know it's risky, but with the SGS and no real working Kies, I was still stuck on 2.1 until a few months ago so I had to take the plunge. Then of course I got hooked. . .
I'll write again if this actually becomes successful
sanosoke said:
Thanks xsenman, removing those two things seemed to work! Took me into recovery at least, still seeing if I can make something boot up now.
I use a mac, but I flash just straight on the phone. I know it's risky, but with the SGS and no real working Kies, I was still stuck on 2.1 until a few months ago so I had to take the plunge. Then of course I got hooked. . .
I'll write again if this actually becomes successful
Click to expand...
Click to collapse
just click MY android Collection for KIES ( MAC ) version
Related
Phone was flashed to 2.2, however after shutting down the phone and booting it up again, I get Black SCREEN + glowing buttons.
Device : Samsung i9000 from Bell running flashed 2.2 Rom.
I've tried following this guide :
STAGE 1 (applies only if you are coming from an earlier Froyo build)
* We are now going to flash the XWJM8 firmware again (Éclair), so make sure that you load the files for this firmware in Odin.
* In PIT, load the 502.PIT file
* For PDA, select the ‘CODE_I9000XWJM8.tar.md5’ file and for PHONE, select the ‘MODEM_I9000XXJM4.tar.md5’ file. Leave all others blank.
* Make sure that the Re-partition box is checked. All other settings should be as shown in the screenshot below.
*Sorry can't post link, forum restriction*
After stage 1, Odin says Passed, my i9000 reboots with still a black screen+ glowing buttons.
I want to start Stage 2, however I can't find the file ‘JPO_JPO_U_JPP.tar’ file.
I've looked up for solution for the last 2 days and can't seem to find a solution anywhere.
Things I've tried on my own without sucess :
Flashed again this time with a CSC from bell, I've read that sometimes without CSC flashing can't be done, but even with the CSC files, my phone is still ''bricked''
Anyone have any idea how to fix this? Ultimately, I want to go back on 2.2 but for now, I just want my phone to boot again =(.
Hate to say it but it sounds like yout internal sd card is dead like MANY OTHERS who have flashed... No way to fix except to send for repairs to bell/samsung...
Sent from my GT-I9000M using XDA App
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Isn't there a way to try and access internal sd card?
Have you try doing a factory reset?
Yeah, I've tried doing so, after reading and researching online, I think this could fix my problem.
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
see reply #7
However adb doesn't even reconize the phone =/
terranq said:
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Click to expand...
Click to collapse
I diddnt specifically mean that it was the flashing that did it but it is OBVIOUS that it happened after he flashed right???
It is known that flashing will sometimes "speed up" the death of an already faulty sd card and that is what I meant by my original post...
And PS... The number of people reporting their sd cards failing on stock firmware w/ no lagfix or no previous flashes to "unofficial firmware" is WAY lower than those reporting sd card death after flashing or adding lagfixes, etc...
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
terranq said:
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
Click to expand...
Click to collapse
And again... I did not specifically state that it was the "flashing" that killed the OP's phone. I simply stated that this seems to happen to MANY people after they flash. NOT the same thing...
Did you come to this thread to argue or to help the OP? I simply posted a reply last night stating that it seems his internal SD card is dead so that he could prepare himself for having to send it away for repairs. I did not respond to the OP to get into an arguement with anyone over "what causes the internal SD cards to fail".
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
cuem said:
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
Click to expand...
Click to collapse
@cuem,
Unfortunately... If it is an actual dead internal sd card (which it seems to be since the steps you followed already did not seem to fix the issue) the only way to fix it is to send it back to Bell who in turn will send it off for warranty repair.
IF you have just purchased the phone within the last 30 days (possibly 60 if Bell is still extending the DOA return policy) and you have a receipt you can take it back to Bell and get an exchange.
Again, unfortunately these are your only options to get this fixed...
Sorry to be the bearrer of bad news...
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
cuem said:
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
Click to expand...
Click to collapse
Ooooooo... That is not good. The American Vibrant is NOT the same as out i9000 models.
What you need to do now is search the forums for the homemade jig thread that will force your device into download mode. Search the forums and you will find it.
Be prepared to be "handy" as you will have to build the jig from scratch...
Sent from my GT-I9000M using XDA App
Yeah, I've read about the Jig thing, I've also read about heating your phone with a hairdryer,
I'm currently trying out the hairdryer, but it doesn't work =/
Might have to try the Jig thing, which seems a little complicated with ordering since I'm running out of time =/
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
This has happened to me, I just flashed with an older version, for me JM5 worked fine.
cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
I had the same thing after flash and spent many hours and tried many different methods to get it back up with no success.
I'm leaving the country for Europe on January 2nd for vacation. This was the last thing I needed... Hopefully I get it back before then, but I'm not holding my breath.
cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
Well... At the very least at least the firmware is now correct so you can send it away for repair if you need to...
Sent from my GT-I9000M using XDA App
I followed this guide
http://www.tunandroid.com/content/i...du-firmware-i9000xwjpa-pour-samsung-galaxy-s/
I believe now oneclicklagfix is installed on my device, can I flash again or that'll brick my phone, how do I uninstall oneclicklagfix if I can't boot up the phone but only acesss clockwork mod menu?
Ok guys, I feel this is just the end of the games... I was flashing back the Roto JME fw with the swype keyboard issue fixed that I have just made, when I accidentally unplugged the tab while starting flashing and in downloading mode.
Now all I get is a logo with a phone an alert symbol and a computer .
Windows as well as Odin see it, but I can't do anything, as Odin hangs on waiting for connection, or something like that.
Is there anything I can do?? Or do I really have to take it to the warranty? And if I will have to take it to the warranty will they see I have previously flashed a beta rooted image on it??
Here's what I am talking about
Please I need some help..
Thanks
Is there no recovery mode by buttons like the captivate? I hate seeing all the bricks
Sent from my SPH-P100 using XDA App
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...
Segnale007 said:
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...
Click to expand...
Click to collapse
Ops, it was the driver... damn windows ...
Solved btw.. I just realized I have lots of things to learn ... I have almost died of heart attack when I saw my tab stucked on that logo.. and now its back again..
Thank u falks
You need to make sure samsung kies are not running for sure unistall it and try it again
use odin. that is still download mode. might take you a couple of tries but works. i was in your shoes the other day
Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Segnale007 said:
Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
I've heard plenty of goofy stories about bricking devices over the years. You must conclude the following:
1.Flash your device in a locked room to avoid your wife/ child pulling cables or pressing buttons.
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
3.Read instructions carefully and write the procedure out in your own words if its your first time.
I've been flashing for years and haven't had a brick yet. Not crossing my fingers either because it has little to do with luck and much to do with care. In this way its a lot like making babies...
ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Good advice.
My only semi-bricks (that involved an hour or two of trial and error to unbrick) resulted from some manner of overzealous cable unplugging.
zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
This is what I have done
Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse
ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Well, first of all thanks for ur nice words. Let me just say that I was about to disconnect another device from the hub where the GTAB was attached and flashing at that time, and yea, I accidentally unplugged the GTAB instead of the other device. I may be a moron, thanks, and thankfully not everyone believes themselves as god, which is a good reason to not help other people who are in troubles, even if for stupid things sometimes... If everyone were thinking like u we were probably still at the age of 1400 ...
Mate it wasn't a barb directed at you personally, but you weren't exactly careful were you?
I'm no god... but I've never bricked a device either, and I've been flashing for over five years now. To top it off I've almost never owned a device which could be taken back to the shop (90% of them come from other countries, not my local retailers). Perhaps this has taught me to be careful.
In any case, what I said holds true, and if you ask around I'm certain you find most will agree.
Dude, you have the best avatar! I can't keep my eyes away! Good luck, and don't worry about mistakes - that is one reason this forum exists.
Cannot start my Gtab after trying update JMC
...Hello everybody,
I am really worry about the fact my Gtab doesn't want to switch on after trying to flash it. I tried all process to put it on download mode or recovery but nothing work.
Do you have any idea about it ? Is there a specific procedure to switch on (eg : press power for 1 minutes + blablabla).
My provider doesn't want to take my Gtab in warenty before my contract is activated (the 4th of february).
Thank you for your answer
HELP, I have same problem, please explain how Hemidall can fix it?
Thanks
[email protected]
zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
I also had a semi-bricked VZW Tab, with the phone-triangle-computer warning graphic at start up. (I flashed a new boot loader, and failed to read the instructions closely enough. Either the file was incorrect for my device, or the drivers were not loaded correctly, but my tablet was borked.)
Using heimdall 1.3.2 (with the correct drivers, on a 32-bit windows system), I clicked the "close pc screen" option to clear the warning.
I then held the power button until it turned off, then held vol+ and power to re-enter download mode. Once in download mode, I used heimdall 1.1.1 to flash the zImage from SCH-I800-Stock-Rooted-2.3.5. My tablet (still unrooted, and still stock?) booted, but sat at the SAMSUNG logo for ten minutes or more. (It announced its progress, telling me periodically "five minutes remaining", etc.)
Once it finished, my tablet was revived. I will now follow the above advice and read all instructions very carefully, re-writing them in my own words to ensure I understand what I'm doing, before I try this again.
One year old thread......do you guys ever watch posting dates???
Sent from my GT-P1000 using Tapatalk 2
...like REALLY bricked
bumping this old thread in hopes that someone can point me in the right direction...
Got my p7510 (10.1" wifi retail) stuck pretty badly when trying to restore stock ROM coming from Overcome (it came rooted from ebay). From what I gather from the forums, seems like my bootloader is still locked.
whenever I attempt to flash a BOOTLOADER, PIT, or PDA using ODIN it connects, initializes, and gets stuck on "Flashing boot.img"
I think the recovery partition is damaged. When I boot using Power + Volume Down, I can get to the screen where you select recovery mode or download mode but recovery mode will not load. The screen flickers when I select recovery, but goes nowhere. Download mode works.
I tried using nvflash to force the right software onto it but I get error 0x4 (usb write failed).
There has to be a way to restore the stock bootloader and get this thing running again. Tablet will not boot android at this point. I have been searching the forums for about a week now, anyone have any ideas?
Please take in mind that i am 18, and that i might not understand technical terms..
So i am one to like to try different kinds of custom ROMS on my captivate because, quite frankly, the stock ROM is terrible. Last year i flashed Cognition V.2 but i eventually got tired of it, so i switched to Cappy's GingerBread ROM, but did not like how much battery life it used. SO seeing that Cognition had come out with V.3 a couple weeks later, i decided to try and flash that ROM. And this is where the problems began...
AS you might know, the most common way to flash roms is to use ROM manager, and when i transferred the file to my phone and selected "Install ROM from SD card." Normally the phone would restart and then go into recovery mode..that did not happen. It just stayed on the ATT start up screen. So i reluctantly pulled out the battery after waiting on it for an hour.
This is when i realized that i could not enter recovery mode at all! ive tried the volume button trick along with trying apps that send your phone directly into recovery mode..oh and i also tried using terminal emulator and sending a command to my phone to reboot into recovery mode, THAT did not work.
So after that I decided as a somewhat last resort, i tried the hard reset, (where you dial a number in and it factory resets your phone.) Which was appearantly was the worst idea i could have ever done because now when i boot up my phone it will get past the ATT screen but now my lock screen will randomly turn on and off by itself, like i cannot unlock it, the screen will repeatedly turn itself on...then off every 5 or so seconds.
I am so confused on what i am to do, and im sorta stressing out about this point in time. So please if one of you educated forum readers know how to fix my terrible mistakes, the help would be EXTREMELY appreciated.
Thank you
FYI I own a mac and ODIN does not work
copy odin 1 click onto a USB to anywhere else
AND USE A REAL COMPUTER
Trusselo said:
copy odin 1 click onto a USB to anywhere else
AND USE A REAL COMPUTER
Click to expand...
Click to collapse
Ditto, I also have a mac but you need the windows computer to get you out of this one, oden works wonders, I can tell you from my own learning experience.
meh, ok thank you. I wish there was a non pc way...lol
http://forum.xda-developers.com/showthread.php?t=755265
the search button is your friend.
I'm noticing a trend of people telling people that don't know what they are doing to use Odin 1 click without ever even asking what build there phone is. Please stop. For some people it has the potential to put them in an even worse situation then they were when they first asked for help.
whiteguypl said:
I'm noticing a trend of people telling people that don't know what they are doing to use Odin 1 click without ever even asking what build there phone is. Please stop. For some people it has the potential to put them in an even worse situation then they were when they first asked for help.
Click to expand...
Click to collapse
+1 bad advice is dangerous
FaithFor_TheFallen said:
Thank you
FYI I own a mac and ODIN does not work
Click to expand...
Click to collapse
look for odin one click with the 3button fix, get virtual box or boot camp, get windows 7 preferably but xp is ok, get drivers, add the phone in donwload mode to the device list on the virtual machine and then you should be able to odin flash from the virtual mache. i have done it in linux but i have also had problems getting it to mount the phone in the virtual machine with a different linux install, i still dont know what the problem was or if you will have problems on the mac.
FaithFor_TheFallen said:
Please take in mind that i am 18, and that i might not understand technical terms.
Click to expand...
Click to collapse
I'm 18 and take offense to that.
FaithFor_TheFallen said:
meh, ok thank you. I wish there was a non pc way...lol
Click to expand...
Click to collapse
Macs are PCs. With a fruit logo.
Sent from my Captivate.
MikeyMike01 said:
I'm 18 and take offense to that.
Macs are PCs. With a fruit logo.
Sent from my Captivate.
Click to expand...
Click to collapse
Your only 18, with your music taste I figured you were mid thirties
Ok so I purchased an i9000M that was advertised as broken (got it for cheap) to see if I could get it going for my step daughter. I turn it on.... I get the samsung boot screen and goes black when it should be booting OS.
Windows still recognizes it somewhat. If I look in device manager under "portable devices" It shows a "j" and "k" drive that are identified as i9000 and i9000 sd or something like that. Although Windows sees it.... It wont mount these drives unfortunately.
Things I've tried ( Before someone suggests I use a JIG............. It doesn't and will not work on this phone)
USB JIG (tested and working on my Hercules)
SD Card Partition (EXT4 and FAT32) because I suspect borked internal storage
SD Card Partition (ReiserFS and FAT32) Still nothing......... then I realized the phone probably wasnt rooted
3 button combos ( every single combination) nada
plugging in USB cable while holding volume up and down...
ADB Reboot recovery/download ( not recognized because I cant turn on debugging)
ETC ETC ETC........
I have been searching google for hours for some kind of clue as to what can be done other than JTAG repair and All I come up with (no matter what site im on) is " Use a USB JIG" duhhhh Its getting rather annoying.
Im no stranger to flashing ( no expert) but this one has me stumped. I was considering buying a RIFFbox anyways but I thought maybe some experienced users out there might be able to suggest something.
My hope is that something can be done with the J and K drive that was mentioned. Perhaps I can format and somehow push a rom straight to the internal storage without any assistance from the phone itself...... I know..... wishful thinking. or perhaps boot straight from external SD???? That would be interesting!
More to this.... I realize this question has probably been asked a million times because it seems to be a common issue on this phone but I suppose my long winded question really boils down to my last paragraph which I havent seen suggested yet.
EDIT: I have a Windows 7 AND kubuntu 12.04 dual boot if any suggestions require linux
Any help would be greatly appriciated.
kibosh1981 said:
Any help would be greatly appriciated.
Click to expand...
Click to collapse
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
xsenman said:
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
Click to expand...
Click to collapse
Thanks. i will have a look and experiment tomorrow.
I'll report back my progress
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
taz0697 said:
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
Click to expand...
Click to collapse
As I mentioned.... no download mode, therefore.... No ODIN. Unless someone has some magical way to make it work otherwise. The computer knows its an I9000 at least. Kies says its in the wrong mode and I have no UI so debugging is out of the question.
Also: Xsenmen. I was unable to get any of the tools to connect. In one section you mention that AndroPlatina attempts to connect while booting? I was unable to get this to happen. I even tried the "heat trick" to no avail
So I'l start off by saying I found this forum, from a freind who said that you guys on this forum could help me with the problem I'm having.
So I have a normal Samsung S Plus. It was rooted. And It was already overclocked, but the preformance was still bad. So someone recomended me to update my Samsung version or install a custom ROM. I talked to a guy who also had the same phone as me and told me about this ROM. I read up alot about how to install them and everything, so I did it. I installed the ClockworkMod Recovery(the touch version) I put the rom on my phone and followed a tutorial on how to install it. It went all good and it said that the rom was installed succsesfully. So to finish the proccess I had to reboot my phone, so I did. The reboot took abit longer than normal and it was expected, but the phone went back to the recovery main menu, I rebooted again hopeing it would resolve it self, but it didn't. I rebooted the phone like 10 times but it kept going to the main recovery menu. So I read up on alot of things on how to fix it and contacted alot other to try and help me, none of the things helped, it always went back to the main recovery menu.
I actully called my phone company and they gave me a number of a phone service, so I brougth the phone to them, I waited for about 2 days for them to get back to me. So when they did, they said that my phone was broken? They didn't say how or why they just said that I broke the phone somehow by trying to install a new version of Android and they said that the reapir would cost me 220 Euros. If you're from Europe you would see that that is a complete rip off. Offcourse I didn't pay them, I just got my phone back in the same state that it was when I gave it to them
So to shorten this topic, I'm looking for a solution to fix my phone myself, without having to pay loads of money, that I dont have.
Basicly my phone is stuck on the ClockwordMod Recovery main menu screen. I can't do anything outside of that. I can edit stuff with the options the mod gives me.And I can put stuff on my SD card if I take the card out of my phone and into my laptop.
If anyone on this forum can help me, please comment bellow. I would be really greatfull to anyone that can give me some tips on how to fix this.
Thanks for reading.
Does download mode work?
Skickat från min GT-I9000 via Tapatalk 2
mreminemfan4ewver said:
So I'l start off by saying I found this forum, from a freind who said that you guys on this forum could help me with the problem I'm having.
So I have a normal Samsung S Plus. It was rooted. And It was already overclocked, but the preformance was still bad. So someone recomended me to update my Samsung version or install a custom ROM. I talked to a guy who also had the same phone as me and told me about this ROM. I read up alot about how to install them and everything, so I did it. I installed the ClockworkMod Recovery(the touch version) I put the rom on my phone and followed a tutorial on how to install it. It went all good and it said that the rom was installed succsesfully. So to finish the proccess I had to reboot my phone, so I did. The reboot took abit longer than normal and it was expected, but the phone went back to the recovery main menu, I rebooted again hopeing it would resolve it self, but it didn't. I rebooted the phone like 10 times but it kept going to the main recovery menu. So I read up on alot of things on how to fix it and contacted alot other to try and help me, none of the things helped, it always went back to the main recovery menu.
I actully called my phone company and they gave me a number of a phone service, so I brougth the phone to them, I waited for about 2 days for them to get back to me. So when they did, they said that my phone was broken? They didn't say how or why they just said that I broke the phone somehow by trying to install a new version of Android and they said that the reapir would cost me 220 Euros. If you're from Europe you would see that that is a complete rip off. Offcourse I didn't pay them, I just got my phone back in the same state that it was when I gave it to them
So to shorten this topic, I'm looking for a solution to fix my phone myself, without having to pay loads of money, that I dont have.
Basicly my phone is stuck on the ClockwordMod Recovery main menu screen. I can't do anything outside of that. I can edit stuff with the options the mod gives me.And I can put stuff on my SD card if I take the card out of my phone and into my laptop.
If anyone on this forum can help me, please comment bellow. I would be really greatfull to anyone that can give me some tips on how to fix this.
Thanks for reading.
Click to expand...
Click to collapse
You have a bootloop into Recovery. Don't worry, it's not a "serious" problem, I had that too, first time I flashed CM. Fortunately, [email protected] has a great and easy solution for this (it worked for me and for many others).
You don't need to pay anything just flash this and bootloop into recovery will never happen again: link.
Hope it helps!
educk said:
You have a bootloop into Recovery. Don't worry, it's not a "serious" problem, I had that too, first time I flashed CM. Fortunately, [email protected] has a great and easy solution for this (it worked for me and for many others).
You don't need to pay anything just flash this and bootloop into recovery will never happen again: link.
Hope it helps!
Click to expand...
Click to collapse
This migth actully solve my problem, but I'm running into a problem.
Odin wont recognize my phone. It doesn't say added in the program. Any tips on how to fix that?
mreminemfan4ewver said:
This migth actully solve my problem, but I'm running into a problem.
Odin wont recognize my phone. It doesn't say added in the program. Any tips on how to fix that?
Click to expand...
Click to collapse
Download Odin Multidownloader 4.43. Open it up in your computer.
Boot into download mode by powering off the phone, than with the phone off, hold down Volume Down + Home + Power until you get into Download Mode. Now plug in your USB cable.(connect your phone), if you have Windows 7, wait for installing the Odin driver, (it installs automatically) and then you should see ADDED !!! in Odin.
Than follow the instructions from point 3:
3. Select OPS - AriesVE.ops (UnZip from AriesVE.zip)
4. Select BOOT - Boot_loader.tar
5. Flash it and bootloop into recovery never gona happen.
You can download all files from here: (All credits go to [email protected], original post: Fix for recovery bootloop problem)
thanks you sooooo much, this finnally fixed it. You saved me from spending a ton of money for a fix. I can't thank you enough
mreminemfan4ewver said:
thanks you sooooo much, this finnally fixed it. You saved me from spending a ton of money for a fix. I can't thank you enough
Click to expand...
Click to collapse
Good! I glad I helped!