Related
Hi, I have a SS/ATT Galaxy S. It was working fine. I made the mistake of running an update to change the ATT splash screen. The device boots to the ATT splash screens and stays there. You can hear the SS start up sounds as though the unit booted ok.
I've tried various Odins they all hang on file analysis. I've tried using different computers per the recommendations in the various threads. I've tried many of the one click and also separate file updaters. They all hang on file analysis.
I am able to use Droid explorer to view the device. I've also put a new update.zip on an sd card but nothing seems to change the splash screen.
I'm not sure how to tell what version the unit is currently on.
I can get to the 3 button state. It says Android System recovery <2e>.
I have the options to reboot, reinstall packages, delete all user data and delete cache data. I've tried each of them, no change.
I have tried to read many threads before bothering anyone. Your input would be appreciated.
Thanks
if you have the update.zip on your phone, in the root of your SD card.. then from 2eRecovery, select reinstall packages.. may have to do it twice. That will boot your phone into clockworkmod recovery.. and from there you should be able to mount storage- put a ROM on your device, flash and be good to go.
Reply to thread
Hi, Thanks for the fast response. I've tried update.zip on both an sd card and also via droid explorer, about 5 times. If I reboot, same thing, the ATT splash is there, and the Galaxy boot sound. I can get into recovery and droid explorer works. If I try Odin it hangs on file analysis. Anything else I can try? Thanks again.
Are you in dl mode when you try this, or recovery?
The phone is now bricked. I was in recovery mode as I saw the 3 button posts on holding the up/down and pwr. I just tried it with dl mode and odin3 and bricked it.(based on another forum's input to check repartition I think). Now it won't boot at all but I'm still able to get to dl mode but not sure what to run to fully recover.
Delphin9 said:
The phone is now bricked. I was in recovery mode as I saw the 3 button posts on holding the up/down and pwr. I just tried it with dl mode and odin3 and bricked it.(based on another forum's input to check repartition I think). Now it won't boot at all but I'm still able to get to dl mode but not sure what to run to fully recover.
Click to expand...
Click to collapse
If you can get to dl mode try using AIO Captivate to flash back to stock 2.1. I've had success as I flashed with the partition checked and had to go all the way back using ODIN contained in the AIO Captivate program. Found here
Delphin9 said:
The phone is now bricked. I was in recovery mode as I saw the 3 button posts on holding the up/down and pwr. I just tried it with dl mode and odin3 and bricked it.(based on another forum's input to check repartition I think). Now it won't boot at all but I'm still able to get to dl mode but not sure what to run to fully recover.
Click to expand...
Click to collapse
Yeah if you can get into download mode than you are not bricked. I would Odin or Heim back to JF6 and go from there. What happened when you tried reinstalling packages from 2e? I know you said everytime you reboot- but what did it say when selected reinstall packages?
Sent from my SGH-I897 using XDA Premium App
I'm back to 2.1, baseband I897UCJF6, Kernal 2.6.69, Eclair. Thanks to everyone for your very kind help. Much appreciated.
Delphin9 said:
I'm back to 2.1, baseband I897UCJF6, Kernal 2.6.69, Eclair. Thanks to everyone for your very kind help. Much appreciated.
Click to expand...
Click to collapse
Great.. glad to hear it
Sent from my SGH-I897 using XDA Premium App
Delphin9 said:
I'm back to 2.1, baseband I897UCJF6, Kernal 2.6.69, Eclair. Thanks to everyone for your very kind help. Much appreciated.
Click to expand...
Click to collapse
Now on to some real ROM flashing!! Glad you got it working. I did almost the same thing and was sweating bullets.
Yeah, it was quite scary. I actually purchased some 100k resistors on Ebay but didn't need to make the jig.
Can you recommend a good set of f/w to load? Is it worth it to move to 2.3?
Cheers...
Delphin9 said:
Yeah, it was quite scary. I actually purchased some 100k resistors on Ebay but didn't need to make the jig.
Can you recommend a good set of f/w to load? Is it worth it to move to 2.3?
Cheers...
Click to expand...
Click to collapse
Of course it is worthed it to move to 2.3 I mean, it comes with so many more features and is running just perfect as a everyday rom. You shouldn't be disapointed
Sent from my Mosaic powered I896 using Tapatalk
But, just in case, out wouldn't hurt to have a proper jig laying around. I'm just saying...
mrhaley30705 said:
But, just in case, out wouldn't hurt to have a proper jig laying around. I'm just saying...
Click to expand...
Click to collapse
+1.
I had to make a jig when I soft bricked it. Not fun. Since then I purchased one and am glad I did.
Well, that means I won't have wasted my $2.00.
I saw this and thought it worth to try. http://www.youtube.com/watch?v=D0aoabVtPJ8
In your footer, it says you're using mosaic.
e.g. ROM: Mosaic III, ¤Kernel: Xcal's #14, ¤Modem: JK4, ¤Launcher: ADW Ex
Can you point me to the correct files/process? I guess I'm scared of screwing it up again. when I look on the forum there's almost too much info for a noob to choose which is best. Cheers...
I'm so embarrassed to post this, but there we go.
CWM installed following the tutorial for the P920 using the 3D ROM MANAGER (rooted by superoneclick). Apparently installed successfully, but when trying to install the mod's ROMs (King_3d, and ThiaiZ KINGDROID), all of them will not boot completely and then turn off your device as you pressed the power button.
Trying to see what could be wrong, I saw on the back label that my device it's a P925. I was stupid and not able to make the backup old ROM.
I just killed my phone or there is still way out of it?
PS: I tried to run this rom from here http://forum.xda-developers.com/showthread.php?t=1270832 but this also does not boot completely, and the device shutting down.
Maybe a problem with the CWR?
Ratzenberger said:
I'm so embarrassed to post this, but there we go.
CWM installed following the tutorial for the P920 using the 3D ROM MANAGER (rooted by superoneclick). Apparently installed successfully, but when trying to install the mod's ROMs (King_3d, and ThiaiZ KINGDROID), all of them will not boot completely and then turn off your device as you pressed the power button.
Trying to see what could be wrong, I saw on the back label that my device it's a P925. I was stupid and not able to make the backup old ROM.
I just killed my phone or there is still way out of it?
PS: I tried to run this rom from here http://forum.xda-developers.com/showthread.php?t=1270832 but this also does not boot completely, and the device shutting down.
Maybe a problem with the CWR?
Click to expand...
Click to collapse
Just follow these directions: http://forum.xda-developers.com/showthread.php?t=1257588
Sent from my LG-P925 using XDA App
CallMeAria said:
Just follow these directions: http://forum.xda-developers.com/showthread.php?t=1257588
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
Thanks, but i have no system running on phone to do this. I´m stuck on CWR with no rom.
How much battery do you have left? You should be able to boot completely with O3D ROMs, and for sure with the stock Thrill ROM. Also, are you doing a data wipe before hand?
If you can get into recovery, which sounds like you can, no need to reflash the recovery. As well, a boot loop usually means failure to wipe properly or wrong kernel (but that doesn't apply here at all).
pjcforpres said:
How much battery do you have left? You should be able to boot completely with O3D ROMs, and for sure with the stock Thrill ROM. Also, are you doing a data wipe before hand?
If you can get into recovery, which sounds like you can, no need to reflash the recovery. As well, a boot loop usually means failure to wipe properly or wrong kernel (but that doesn't apply here at all).
Click to expand...
Click to collapse
Battery it´s full! All attempts i wape the cache , data & factory, and dalvik too.
Without success, the phone keeps Shutting Down after booting the ROM's. (I can see "reading sd card" on the top bar before shutting down screen.
Thank you in advance for the assistance.
Ratzenberger said:
Battery it´s full! All attempts i wape the cache , data & factory, and dalvik too.
Without success, the phone keeps Shutting Down after booting the ROM's. (I can see "reading sd card" on the top bar before shutting down screen.
Thank you in advance for the assistance.
Click to expand...
Click to collapse
Wait so you're actually able to boot into the operating system and then it just shuts off? Or does it reboot back to the boot screen? If its shutting off That sounds like something is wrong with the phone itself.
Try to redownload a fresh copy of the rom and push it to your SD card (check the md5 sums to be sure its right. If its not posted ask the dev to put it up). Boot into clockworkmod and go to mounts and storage. From there format /system /data and /cache. Now install the rom and reboot.
Sent from my LG-P925 using XDA App
CallMeAria said:
Wait so you're actually able to boot into the operating system and then it just shuts off? Or does it reboot back to the boot screen? If its shutting off That sounds like something is wrong with the phone itself.
Try to redownload a fresh copy of the rom and push it to your SD card (check the md5 sums to be sure its right. If its not posted ask the dev to put it up). Boot into clockworkmod and go to mounts and storage. From there format /system /data and /cache. Now install the rom and reboot.
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
Thanks to help-me again
I followed exactly as you instructed. Now with the ROM ThiaiZ again without success. Booting ROM (Break Dancing Droid) and then Power off
Shutting Down Screen
Ratzenberger said:
Thanks to help-me again
I followed exactly as you instructed. Now with the ROM ThiaiZ again without success. Booting ROM (Break Dancing Droid) and then Power off
Shutting Down Screen
Click to expand...
Click to collapse
There's no reason for the phone to shut off like that. Even if you are getting bad rom flashes. Unless..
I gotta ask...is the battery charged? You can lose a lot of battery being in recovery and going through reboots. It could actually be that the battery is not charged or is defective. Try charging and/or replacing the battery.
Sent from my LG-P925 using XDA App
CallMeAria said:
There's no reason for the phone to shut off like that. Even if you are getting bad rom flashes. Unless..
I gotta ask...is the battery charged? You can lose a lot of battery being in recovery and going through reboots. It could actually be that the battery is not charged or is defective. Try charging and/or replacing the battery.
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
I have good news! Or bad news too. I just decided to turn on the device with the USB cable plugged in and booted it as well. He is not holding battery charge, consisting as 0% of charged. I tested another battery from a friend and did the same thing. If I unplug the USB cable the device shutting off immediately. It may be a software problem or a hardware problem coincidentally?
Ratzenberger said:
I have good news! Or bad news too. I just decided to turn on the device with the USB cable plugged in and booted it as well. He is not holding battery charge, consisting as 0% of charged. I tested another battery from a friend and did the same thing. If I unplug the USB cable the device shutting off immediately. It may be a software problem or a hardware problem coincidentally?
Click to expand...
Click to collapse
Edit: it appears they're having the same problem over in the O3D forums. Try restoring the stock firmware and stock recovery. I would also try formatting all your partitions individually (you will lose data so backup first).
Sent from my LG-P925 using Tapatalk
DELETED.
Sent from my LG-P925 using Tapatalk
CallMeAria said:
Edit: it appears they're having the same problem over in the O3D forums. Try restoring the stock firmware and stock recovery. I would also try formatting all your partitions individually (you will lose data so backup first).
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
I set my phone for Stock & Recovery firm, unrooted. Nothing doing! I give up, nobody knows how to solve this problem. I'm totally frustrated with it.
I was trying to root and install a custom ROM on my phone when this happens.
I suffered 3 kinds of brick that I recognized from reading the forum's guides.
So here's the story:
I install SuperUser and CWM through the stock recovery mode.
After that I tried to wipe everything with CWM from my phone as I wanted to downgrade from my update Official ICS back to the stock GingerBread ROM. (This is to prevent any problems to install the new custom ICS. Read on forum also*)
During the wipe, CWM got stucked at somewhere at the start of the process (Forgotten what it was). It was about more than 15minutes before I made my decision to stop it by holding the power button. Obviously this caused a bootloop or something like a soft brick (Stuck at boot screen).
After the first brick encounter, I tried to fix it by flashing the stock GingerBread ROM directly with Odin without wiping anything as it was stucked in the first step. By doing this, I think I had a Super Brick as the installation also got stucked at loading factoryfs.img image file. There's no solution to this as I looked up in the forums for quite some time.
So, I cancelled the installation and my phone wouldn't start up again. There's no sign of battery charging when plugged in and it wouldn't start by holding the power button. Unable to access recovery/download mode. Odin also didn't recognize my device.
Can anyone here kindly advice me on what should I do now? In deep sad mode -.-
cyyong95 said:
I was trying to root and install a custom ROM on my phone when this happens.
I suffered 3 kinds of brick that I recognized from reading the forum's guides.
So here's the story:
I install SuperUser and CWM through the stock recovery mode.
After that I tried to wipe everything with CWM from my phone as I wanted to downgrade from my update Official ICS back to the stock GingerBread ROM. (This is to prevent any problems to install the new custom ICS. Read on forum also*)
During the wipe, CWM got stucked at somewhere at the start of the process (Forgotten what it was). It was about more than 15minutes before I made my decision to stop it by holding the power button. Obviously this caused a bootloop or something like a soft brick (Stuck at boot screen).
After the first brick encounter, I tried to fix it by flashing the stock GingerBread ROM directly with Odin without wiping anything as it was stucked in the first step. By doing this, I think I had a Super Brick as the installation also got stucked at loading factoryfs.img image file. There's no solution to this as I looked up in the forums for quite some time.
So, I cancelled the installation and my phone wouldn't start up again. There's no sign of battery charging when plugged in and it wouldn't start by holding the power button. Unable to access recovery/download mode. Odin also didn't recognize my device.
Can anyone here kindly advice me on what should I do now? In deep sad mode -.-
Click to expand...
Click to collapse
my suggestion is to read this and run before you get bombarded http://forum.xda-developers.com/showthread.php?t=1321268
I think you dont know what you are doing, as you dont know where to post so i think its better off you dont do anything with your phone
It should be in Q&A forum....Moderators please move it to appropriate forum.....
Stop irritating him. How do you feel if your phone got bricked and don't know what to do.
Coming to the topic. You did not follow basic steps, you used the wrong method of rooting that to on ICS. Don't think that your phone is bricked. Did you flash any custom kernel. I think you were trying too many things and your phone is dead. This happened to me once, I thought my phone is bricked and didn't know what to do. But I remembered I had a external battery adapter charger and charged my battery separetly and know what it worked. Try charging your phone separetly.
Sent from my GT-N7000 using xda app-developers app
Bro you should've use abyss kernel with red pill to downgrade to gb... cwm has some sort of bug even if its fixed . Be on the safe side and flash abyss
Sent from my GT-N7000 using xda premium
I have to place my threads in the correct category, and so do you.
first move to the right place
second give more details of what you have done, the steps, the kind of kernel, rom, otherwise we cant give you accurate solutions
Sent from my GT-N7000 using XDA
Start Thread and ask for donations, that's what we all do here.
Yes...I see that's the trend here... I suggest when they got, just buy themself an SG3
xlfate said:
Bro you should've use abyss kernel with red pill to downgrade to gb... cwm has some sort of bug even if its fixed . Be on the safe side and flash abyss
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Agree..use abyss kernel to wipe anything bfore flash any ics rom for ur own safety
Sent from my GT-N7000 using xda premium
Samsung service seems the only solution as you can't get into dl or cwmr modes.
Sent from my GT-N7000 using xda premium
http://forum.xda-developers.com/showpost.php?p=28744408&postcount=5713
This great solution comes from rocket thread, where else.
Galaxtus said:
Stop irritating him. How do you feel if your phone got bricked and don't know what to do.
Coming to the topic. You did not follow basic steps, you used the wrong method of rooting that to on ICS. Don't think that your phone is bricked. Did you flash any custom kernel. I think you were trying too many things and your phone is dead. This happened to me once, I thought my phone is bricked and didn't know what to do. But I remembered I had a external battery adapter charger and charged my battery separetly and know what it worked. Try charging your phone separetly.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I'll post it in right forum to get my queries answered..better to follow the rules...its not hard to understand.better to spend ur valuable time to read it and posting in the appropriate forum to get correctly answered rather than opening topics. Just a suggestion...
Nw come to the point. Please explain the situation what u did and what files u flashed? XDA are always here to help you.
Sent from my GT-N7000 using XDA Premium App
cyyong95 said:
I was trying to root and install a custom ROM on my phone when this happens.
I suffered 3 kinds of brick that I recognized from reading the forum's guides.
So here's the story:
I install SuperUser and CWM through the stock recovery mode.
After that I tried to wipe everything with CWM from my phone as I wanted to downgrade from my update Official ICS back to the stock GingerBread ROM. (This is to prevent any problems to install the new custom ICS. Read on forum also*)
During the wipe, CWM got stucked at somewhere at the start of the process (Forgotten what it was). It was about more than 15minutes before I made my decision to stop it by holding the power button. Obviously this caused a bootloop or something like a soft brick (Stuck at boot screen).
After the first brick encounter, I tried to fix it by flashing the stock GingerBread ROM directly with Odin without wiping anything as it was stucked in the first step. By doing this, I think I had a Super Brick as the installation also got stucked at loading factoryfs.img image file. There's no solution to this as I looked up in the forums for quite some time.
So, I cancelled the installation and my phone wouldn't start up again. There's no sign of battery charging when plugged in and it wouldn't start by holding the power button. Unable to access recovery/download mode. Odin also didn't recognize my device.
Can anyone here kindly advice me on what should I do now? In deep sad mode -.-
Click to expand...
Click to collapse
Have you read the post quoted below?
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Please read and see if it helps. Or maybe you have already tried the process outlined.
All the best to you.
I'm sorry to post in the wrong section of the forum. It was my mistake to not read instructions carefully.
Now I have sent it to the service center and waiting for their response. But I didn't do anything like put my phone in the microwave or anything.
So does that means they will find out that I did something to my phone and void my warranty?
smaiitm said:
Have you read the post quoted below?
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Please read and see if it helps. Or maybe you have already tried the process outlined.
All the best to you.
Click to expand...
Click to collapse
Thank you very much for the help but it was too late as my phone is already confirmed hard bricked.
Will try it if I got the chance to bring my phone back to life.
Changed a new note from samsung service LOL
cyyong95 said:
Changed a new note from samsung service LOL
Click to expand...
Click to collapse
Great! Have Happy Times Flashing Safely! Cheers.
Hi, I need some advice. I dropped my Galaxy S in a puddle. It was submerged for the just a second, but when I fished it out, the screen had gone 'weird', so I got the battery out as quickly as possible, then dried it out for a few days in the airing cupboard. I then tried it and it started up okay, then when I swiped to unlock the screen, it froze. since then I have been unable to boot the phone. It shows the Galaxy logo, then restarts and continues that loop.
I wondered if maybe the software has just been corrupted during its bath, so I thought i might try flashing a ROM onto it to see if that would recover. I found that I could not enter recovery mode but download mode opened okay. I have tried flashing a few ROMS using Odin. I am completely new to this and have never flashed my phone before, so steep learning curve. I have so far tried - I9000XWJW5 which I believe is normally used before installing Cyanogen mod. I also downloaded the T-Mobile Stock ROM and one with this filename - CF-Root-XX_OXA_JW4-v4.4-CWM3RFS. All of these successfully downloaded to the phone and I could see the progress bar on the phone. Unfortunately I still cannot get the phone into recovery mode.
So, whats your opinion? is my phone screwed? Is there anything else I can try which may help, like formatting or anything like that.
Any help would be very much appreciated.
try search for value pack 2.3.6 and flash it then root it after that I believe you should get the recovery option.
erpurohit said:
try search for value pack 2.3.6 and flash it then root it after that I believe you should get the recovery option.
Click to expand...
Click to collapse
Unfortunately I think that was the file - I9000XWJW5 I had already tried.
did you rooted your phone after flashing
erpurohit said:
did you rooted your phone after flashing
Click to expand...
Click to collapse
Can I do that without being able to get into recovery mode?
I've just been reading that I can use a PIT file to repartition during flashing. Is it worth trying? I noticed in the Value pack TAR file it does not have a PIT file. I got one downloaded from somewhere else called - s1_odin_20100512.pit worth a shot?
I tried including the pit file as well. Odin reported success but phone is still continuous boot loop and I cannot get recovery mode up. Do you think one of those USB things that get you into download mode would help? I'm beginning to think the internal SD is knackered, or something like that.
I think the memory is brocken but i don't realy know. Send it to Samsung for a check
Sent from my GT-I9001 using xda app-developers app
I'll try them, will they still help me after I've tried reinstalling ROM etc?
Yes they will repair it if you pay for
Sent from my GT-I9001 using xda app-developers app
Credits to-
BigBearEvo- For making important modifications.
kashttl- For informing about errors with ROM Toolbox.
Introduction-
In simple language, bricking is just making your phone unusable. But as we go deeper in this world of rooting, we find ourselves reading posts with terms like “soft-brick” and “hard-brick”. So what is the difference?
Hard-brick
Hard-brick is when you mess up with your boot image while updating, or when you snatch your phone's USB cable while an update is going on through PC. Or even worse, you flash a ROM @ 0% battery.
Soft-brick
Soft-brick is when you fail to clear your Dalvik, forget to format/wipe data, which leads to your phone going into a bootloop i.e- keeps playing bootanimation for a long time (15 mins or more). This generally happens when there is some mismatch of Android Virtual Machine with installed apps. Or for us, the phone is stuck in White HTC logo screen.
So how to get your phone back to life in case of-
Hard-brick
Sorry boss but your phone is dead. Reviving it will be more expensive than buying a new one. Also this task is done only by a few specialists.
Hard brick can be solved in case of improper flashing of RUU or updates on Stock Phones. you require USB drivers to be installed along with HTC Sync.
You Need the proper RUU designed for your area model.
Load phone into Bootloader screen. Run RUU from PC. you may have to do this several times and follow instructions carefully. You will eventually you load the RUU and have a working phone.
This isn't for the Noob to do. Recommendation is see a service engineer, or seek good help from users that have done this. each Hard brick can be different, dependent on what they did in the first place
Soft-brick
Hmmmm.. Something can be done-
A> First pull out your battery.
B> Put it back.
C> Press Power and Volume Down simultaneously till you enter fastboot screen.
D> Get into recovery mode.
Now you have 2 options-
i> Restore to one of your previous backups.
ii> Flash stock ROM or some other stable ROM.
Precautions while flashing-
A>Firstly DO NOT flash using ROM Toolbox or apps with similar functionality. (Credits- kashttl). People from HTC Desire forum faced a lot of hassle in doing so.
B> Don't just snatch your USB Cable while transferring ZIP file from PC to SD card. It will lead to CWM recovery Errors.
C> Have at least 50% battery charge in your phone before flashing any ROM, minimal level is 20% as 5% battery is used when flashing.
D> Always do a Triple wipe before flashing ROM. (Data/Cache/Dalvik)
E> Always do a Nandroid backup of current ROM before changing into a custom one. (Recovery or Rom manager)
F> Follow any other special instructions (If any) while flashing.
G> If you end up with any problems with a certain ROM, please post in the ROM thread ASAP.
Disclaimer-
YOU the users are solely responsible for anything you do. We the developer supply this for your benefit. Failure to follow the rules/guides will possibly result in defective or inoperable phones which we are not responsible for.
Amazing guide. Bookmarked for future use
Btw thanks for mentioning me
Sent from my HTC Salsa C510e using xda app-developers app
kashttl said:
Amazing guide. Bookmarked for future use
Btw thanks for mentioning me
Sent from my HTC Salsa C510e using xda app-developers app
Click to expand...
Click to collapse
You do something good for us and you surely get mentioned.
Sent from my GT-P3100 using Xparent Cyan Tapatalk 2
WOah! dude, you got a sticky man! Awesome!
stuck at exclamation mark
Hey there, I'm following the soft brick steps but it got stuck at the exclamation mark logo after i get into the recovery mode. what should i do? please help
Remove battery count to ten. Reinsert and boot normally. I'm assuming you have tried to update with and ota. This will not work and u will constantly get this screen and problem.
BigBearEvo said:
Remove battery count to ten. Reinsert and boot normally. I'm assuming you have tried to update with and ota. This will not work and u will constantly get this screen and problem.
Click to expand...
Click to collapse
I tried it but my phone keeps playing the bootanimation over and over again
Remove battery and get to hboot menu. Hold volume down key then then power on while holding down.
If u have recovery, boot into it and wipe everything. If not, factory reset on hboot and try to reboot. Seems what ever u did has buggered it and u have to start over.
BigBearEvo said:
Remove battery and get to hboot menu. Hold volume down key then then power on while holding down.
If u have recovery, boot into it and wipe everything. If not, factory reset on hboot and try to reboot. Seems what ever u did has buggered it and u have to start over.
Click to expand...
Click to collapse
Thanks BigBearEvo i did what you asked me and the phone works fine now. Some of the data may have lost but its okay. Thanks again!
Hi Vigoos,
I tried the steps you have mentioned above, but i dont have any backups saved. Can you please let me know what is the procedure to flash a stock ROM.
Thanks.
ravikeerthi88 said:
Hi Vigoos,
I tried the steps you have mentioned above, but i dont have any backups saved. Can you please let me know what is the procedure to flash a stock ROM.
Thanks.
Click to expand...
Click to collapse
Depends on the stage you got to. did you try to flash an RUU for your area? if you did it would have wiped your recovery program off. if your didnt and still have cwm installed, please go to another rom that takes your fancy and follow flashing guides from there. more info would be helpful though.
BigBearEvo said:
Depends on the stage you got to. did you try to flash an RUU for your area? if you did it would have wiped your recovery program off. if your didnt and still have cwm installed, please go to another rom that takes your fancy and follow flashing guides from there. more info would be helpful though.
Click to expand...
Click to collapse
Hi BigBearEvo,
I tried to flash a RUU but the USB was not detectable in the Fastboot mode so the CWM recovery is still intact. Will try the the other option though.
Thanks
ravikeerthi88 said:
Hi BigBearEvo,
I tried to flash a RUU but the USB was not detectable in the Fastboot mode so the CWM recovery is still intact. Will try the the other option though.
Thanks
Click to expand...
Click to collapse
If the USB wasn't detectable it means your pc/laptop does not have the correct programs installed to find it. IE adb etc & java sdk/jdk installed.
try the other methods first though as it should work out easier
Hi BBE,
I was able to flash your Xsense ROM, but after some time it gives force close errors for some of the applications. Please let me know if i have missed anything.
Thanks
ravikeerthi88 said:
Hi BBE,
I was able to flash your Xsense ROM, but after some time it gives force close errors for some of the applications. Please let me know if i have missed anything.
Thanks
Click to expand...
Click to collapse
some force error closes happen from clash of apps, did you completely wipe it....what ext extension are you using?
BigBearEvo said:
some force error closes happen from clash of apps, did you completely wipe it....what ext extension are you using?
Click to expand...
Click to collapse
Hi BBE,
Yes i did a triple wipe before flashing. I'm using ext 3.
ravikeerthi88 said:
Hi BBE,
Yes i did a triple wipe before flashing. I'm using ext 3.
Click to expand...
Click to collapse
when using the rom did u activate links2sd while using int2-ext or data2sd?