Hey guys. I just updated to Wicked Sensations 1.2 from 1.1. I used 1.1 for a few weeks and loved it, naturally I wanted 1.2 when it came out and I read the changelog. So I downloaded it, put it on the ext SD card. Booted to Clockwork Mod Recovery. I did a Nandroid backup. Then I wiped data 3 times, wiped Dalvik cache 3 times, and then installed from zip file. The install went great. I rebooted after it was done and the rom launched fine. I went through the initial setup and restored my Nova Home Screen settings. Then I went to try out the included Wifi Tether app. I launched it, it asked for root access, I granted it. Something didn't work as it was initializing, so I closed it and rebooted the phone, just to make sure all of it's processes were killed and my normal wifi would work normally. On reboot, the phone decided it needed to "Upgrade Apps". So I waited about an hour and it never left that screen. It didn't show me any sort of progress like it had before either when it optimized apps for Jellybean coming from ICS. So I popped the battery out. Now I'm doomed. Stuck on the boot screen with the "SAMSUNG" text with the animated glow effect. I also can't seem to get it into recovery mode to restore any of my backups.
Any thoughts? I'm fairly new to this so don't rule out dumb mistakes. Also, I noticed in the Wicked Sensations 1.2 instructions that I could have upgraded without doing a full data wipe, but it said to do a full wipe and clean install if you had any trouble with the upgrade, so I don't think that is the cause of my problems. Do I need to turn to Odin?
You have a soft brick since you can get up the boot logo screen....time to bust out Odin to save the day.
http://forum.xda-developers.com/showthread.php?t=1941546
Sent from my SPH-L710 using xda app-developers app
Thanks a bunch. I wasn't sweating too bad since I could turn it off and on and see a spark of life in it. Thanks for the link too. I'll confirm success or failure later tonight after a good few hours drive back home.
That fixed it for me. Thanks again.
Related
Has anyone had a similar issue? Know a fix?
I got this phone, activated, ran the stock EC05 rom for a day or so, and decided to root and flash a custom rom. I used syndicate frozen 1.1 with the voodoo kernel and clockworkmod 2.xxx (don't recall now) for the flash. This was following the guide posted in on youtube for syndicate 1.1.0 found in said thread. This tutorial was basically one click root-> wipe the junk 3x-> flash rom-> flash kernel-> wipe junk again-> reboot. First thing I got loading up was a force lose on setup wizard. No options, just a black screen with a task bar. I fought with it, and found that if I removed setup wizard from the rom, it would boot, but no unlock screen, no search button, and no home button among other things. This was done twice to check the installation and re-downloaded in between for integrity.
Now I odin back to stock EC05 with the tutorial for restoring an almost bricked epic, and wipe everything by doing so. The phone boots normal and all is well stock and boring.
Next I decided to upgrade to new software. Flash Clockworkmod purple (newest version), Boot into recovery, wipe junk 3x (Data Cache Delvik) then Syndicate Frozen 1.2-> TwilightZone 1.1.1 (just so I had a different kernel for comparison)-> wipe junk 3x-> reboot. Still force closing on setup wizard.
Final straw: Blow it all away with odin back to stock EC05. All boots and works well. Install 1 click root, boot into recovery with stock rom and wipe data/cache/delvik and wipe the junk. Reboot and BAM, setup wizard force close. It seems as though something is getting trashed by clockworkmod on both versions I tried. I'm not new to debugging, but I've been using the Touch Pro 2 for the last year and a half. This thing is a different animal with the same 1 year learning curve. It's been 5 days. Still getting used to all this. I only followed the tutorials to be sure it was done correctly.
Can anyone report something similar or even a fix for this? I've searched my butt off, but the search terms used to find such a problem are going to throw you insane results no matter what. Coming out of the shadows is my only option.
I tried to keep it short. Sorry.
BoominSVX said:
Has anyone had a similar issue? Know a fix?
I got this phone, activated, ran the stock EC05 rom for a day or so, and decided to root and flash a custom rom. I used syndicate frozen 1.1 with the voodoo kernel and clockworkmod 2.xxx (don't recall now) for the flash. This was following the guide posted in on youtube for syndicate 1.1.0 found in said thread. This tutorial was basically one click root-> wipe the junk 3x-> flash rom-> flash kernel-> wipe junk again-> reboot. First thing I got loading up was a force lose on setup wizard. No options, just a black screen with a task bar. I fought with it, and found that if I removed setup wizard from the rom, it would boot, but no unlock screen, no search button, and no home button among other things. This was done twice to check the installation and re-downloaded in between for integrity.
Now I odin back to stock EC05 with the tutorial for restoring an almost bricked epic, and wipe everything by doing so. The phone boots normal and all is well stock and boring.
Next I decided to upgrade to new software. Flash Clockworkmod purple (newest version), Boot into recovery, wipe junk 3x (Data Cache Delvik) then Syndicate Frozen 1.2-> TwilightZone 1.1.1 (just so I had a different kernel for comparison)-> wipe junk 3x-> reboot. Still force closing on setup wizard.
Final straw: Blow it all away with odin back to stock EC05. All boots and works well. Install 1 click root, boot into recovery with stock rom and wipe data/cache/delvik and wipe the junk. Reboot and BAM, setup wizard force close. It seems as though something is getting trashed by clockworkmod on both versions I tried. I'm not new to debugging, but I've been using the Touch Pro 2 for the last year and a half. This thing is a different animal with the same 1 year learning curve. It's been 5 days. Still getting used to all this. I only followed the tutorials to be sure it was done correctly.
Can anyone report something similar or even a fix for this? I've searched my butt off, but the search terms used to find such a problem are going to throw you insane results no matter what. Coming out of the shadows is my only option.
I tried to keep it short. Sorry.
Click to expand...
Click to collapse
Only wipe 3x before flashing, not after! Wiping after flashing just removes everything you did! Odin to stock ec05, one click root, wipe data/cache/dalvik 3x, flash srf 1.2, flash kernel immediately after, then turn on the phone.
Please click both links below and vote: http://picketfenceblogs.com/vote/3616
http://apps.facebook.com/gerberphotosearch/entry/935/amber.aspx
HAHAHA!!! And the dumbass award goes tooo......
I'm not going to edit though. Just incase someone else goes newb for a minute or 5 days. lol. Nice job on the quick answer though. Thanks
BoominSVX said:
HAHAHA!!! And the dumbass award goes tooo......
I'm not going to edit though. Just incase someone else goes newb for a minute or 5 days. lol. Nice job on the quick answer though. Thanks
Click to expand...
Click to collapse
No problem. The exclamation points were only for emphasis. Don't worry about it, I was the same way just a couple of months ago, just ask around lol.
Please click both links below and vote: http://picketfenceblogs.com/vote/3616
http://apps.facebook.com/gerberphotosearch/entry/935/amber.aspx
yesterday a dialog popped up on my phone to update my phone. I clicked on postpone, thinking it would simply just ask me later. I am running RMK's ROM, and now every time I turn on my phone it turns off and tries to update, but fails. How do I stop my phone from doing this? I don't want the update.
Try either doing a data wipe or flashing another ROM then going back if you want to stay on RMK.
I have also heard wiping the cache from recovery works too.
I'm running RMK's Rom and just caught the update notice just now. PITA it limited deferment to 5 days. Earlier today I didn't catch it in time and had to batt pull after it hung. When I went to recover from a recent nandroid backup it hung trying to boot into CWM. I did get into recovery on the second attempt. Just be sure you have a current nandroid of your stuff.
Shouldv'e dug a little more before posting.
http://forum.xda-developers.com/showpost.php?p=16093933&postcount=383
Sent from my ADR6350 using XDA Premium App
I rooted my Evo for the first time today using the Revolutionary method. Everything went smoothly following the instructions. I downloaded and flashed the latest Evo Classic ROM and I was loving it. It seems to be an awesome ROM. I have 200 MB free space instead of 46MB with all of my apps installed. Everything was great until I went to go to bed. I put the phone on the stock HTC charger and climbed in bed. Less than a minute later it rebooted. The phone has always done that at random times so I didn't think anything of it. Shortly after it booted it rebooted again. It just keeps rebooting over and over as long as it's on the charger! Now it even reboots when it's not charging but the interval is as long as 10 minutes instead of 1.
Has anyone else had this issue? I spent HOURS getting everything just right and customizing settings after flashing this ROM and I really don't want to have to do it all over again. I followed the instructions for flashing the ROM. I cleared the cache and wiped all data. I backed up my apps with Titanium Backup and restored a select number of them. My phone is my alarm clock. Now I can't trust it to wake me up in the morning to go to work!
EDIT: I just restored from my stock NAND backup and it is working fine for tonight. I'm guessing I need to just start from scratch and reflash Evo Classic? I can't seem to find anyone else that had this problem so I assume it was something with my flash or an app I had installed?
I flashed a fresh Evo Classic ROM and started over. Everything was great. I got it all setup and restore my apps. No rebooting problems. Put it on the charger. Worked fine. As a troubleshooting step I opened Sleep, my alarm clock app, and within 30 seconds it rebooted. Obviously something with that app triggered it. I uninstalled it. About a minute later it started a reboot loop in one minute intervals.
Apparently no one has any ideas or I am invisible. I can't post in the Evo Classic thread because I don't have enough posts to earn me the privilege.
Did you wipe dalvik? And what recovery are you using?
I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions.
I only see two options:
Wipe Data/Factory Reset
Clear Cache Partition
I have done both of these each time I flashed. I just flashed again and installed only the Sleep As An Droid app fresh from the market. I opened it and within one minute it rebooted. Obviously this app doesn't agree with this ROM or something isn't going right during the wipe and/or flash.
Any other suggestions for a stable ROM that has the new Sense notification bar with quick settings?
EDIT: I found the Dalvik Cache wipe option under advanced. Doing it now and will reflash and try again.
EDIT 2: Well that failed. I wiped data, cache partition, and dalvik and flashed the ROM. I logged into my Google account, downloaded the app from the market, put the phone on the charger, opened the app, and it rebooted.
Is it rebooting if you don't use that particular app at all?
Evo450 said:
I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions..
Click to expand...
Click to collapse
That recovery is called clockwork. You might think about changing your recovery to amon ra since some people have issues with clockwork because it doesn't properly wipe cache and dalvik
Hey there! Sorry about your issues. I don't always check the q&a, so you are usually better off posting on my thread or pm. I just happened to peep on here today
First. Use this. It's the second step on my instructions to flash Classic. Not necessary, but recommended. http://forum.xda-developers.com/showthread.php?t=705026
Second, don't use titanium backup. Instead, use mybackup root (free in market and included with my Rom). Not to bash tb, but mybackuproot has never given me issues while I've heard stories about tb.
Third, once you get amon ra installed, boot into recovery and wipe everything but your sdcard.
Fourth, download a fresh copy of classic from a reliable network, like home computer. Downloading from a phone is bad news (just a tip since you're newly rooted )
Fifth, flash and enjoy!
Please let me know how it goes for you.
Truly,
Tommy
tapatalk signature here. lovely.
Thank you very much for the reply! I will try your suggestions some time this weekend. I need my phone to work 100% as I am traveling so maybe Sunday I will try again.
I followed all of your suggestions and redownloaded the ROM, installed RA Recovery, cleared all data, cache, and dalvik several times, and reflashed the ROM.
I restored my apps and data using MyBackup Root and it took over 2 hours! I opened my alarm app and... reboot. Back to the same old reboot over and over.
I think I'll just go back to the stock ROM and remove the bloatware and call it good.
Theirs one obvious thing nobody mentioned. Google how to check a md5 sum do that with every rom you download and if it does not say its right don't flash, redownload and check again. Also restore as little as possible through mybackup and if you are restoring things like your alarms or any system settings don't.
As for good roms with quick settings like r2r going green lightning fast, or unleashed r6.
Ps I would suggest useing r2r superwipe before whatever you may flash n wipe both caches a few times first it might help
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
Also id recommend copying all contents of SD card to computer and wipe SD card then reload everything back onto SD card. I know sometimes the SD card can become corrupt and cause bootloops and random reboots
I checked the Md5 sums of everything I downloaded. I only restored my apps, text messages, and Bluetooth pairings. I even ended up buying a new, larger SD card yesterday and I formated and used it when I flashed.
This afternoon I flashed my latest backup of my stock ROM and used Titanium Backup to removed all of the Sprint bloatware. My phone is running very fast now with over 110 MB of internal memory available so I can't complain.
Maybe next weekend I will try another ROM but for now I need me phone to be working since I do not have a land line and I rely on my phone for work.
You said this happened before you ever rooted? Maybe its a factory defect if u got a.warrenty I would suggest unrooting and sending to them.
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Its not normal they keep giveing you defects... I have never heard of.this problem anyway... I would take it bac
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
My girlfriend had the same issue with her second evo. She had the Black Evo at first than a friend of hers swapped her to the white Evo. She had the issue only on the white evo. She ended up having to replace the phone with another one. That one did the same thing for awhile so we thought it was an issue with an app she was running. I have the black evo and made a exact copy of her phone. I never once had the issue.
Sprint ended up replacing it agian with a line that something was different in the white Evo from the black one that was causing the issue. Ever since that day she hasn't had a problem with her phone. I just rooted and did her rom last night.
My question would be does the phone get hot? Or feel hot? The reason I ask is that the phones processor may restart the phone (in effort to cool it down) randomly. That is something to consider.
Glad I got the black
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then
Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
I kept getting the same thing when i flashed classic. I went back to shooter port which runs butter smooth and is fantastic looking with sense 3.0.
DO THIS TO TRY TO GET EVERYTHING WORKING (no more soft reboot)
-connect your sd card to your computer
-copy contents to your computer for a backup
-copy PC36IMG.zip to your sd card make sure it is on root of sd card(attached to message)
-disconnect usb cable then pull battery
-enter bootloader (vol down + power)
-when it asks if you want to install the new update select yes
-after thats done pull the battery again
-enter bootloader then select recovery ( you should now have amonRa 2.3 )
-flash zip from sd card (vrsuperwipe.zip *thanks to virus*)
-go back and go into wipe menu, wipe dalvik-cache, wipe sdext, battery stats, and rotate settings.
-go to partition sd card and partition for a gingersense rom if you have not done so already. (0 swap, 1024 or 2048 ext2, remaining FAT)
ABOVE PROCESS COULD TAKE SOME TIME, MAKE SURE YOUR SD CARD IS MOSTLY EMPTY BEFORE YOU DO THIS (ONLY HAVE PC36IMG.ZIP ON IT)
-select usb mass toggle and connect to computer
-copy over your choice of rom, i suggest the shooter e3d port by team nocturnal.
-flash rom
-go to flash zip from sd card again this time select TeamNocturnal folder and pick a kernel to flash (try all of them if you would like, some phones run better with different kernels. mine runs well with HDMwIn kernel.
-wipe dalvik-cache one more time and you are ready to reboot with no more random restarts hopefully.
good luck - and please hit the thanks button if any of this works for you
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Re: [Q] Any possible ways to unbrick a softbricked SHGI747
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:
MeatwadGetTheHunniesG said:
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:
Click to expand...
Click to collapse
No problem at all =) Its pretty hard to completely brick your device unless you flash something made for a different phone lol. As long as your phone can see any signs of life (even a faint vibration), let us know and we are more than happy to help!
Sent from my SGH-I747 using xda app-developers app
I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.
S.O.S. Phone is completely wiped only dowload mode and recovery work.
Okay so I think I kind of put myself in a sticky situation. I tried to flash a custom rom onto my phone but in the process deleted my modem file everything worked fine except for the fact that I couldnt make calls or text messages. Basically a $400 dollar multimedia device. At this point I just want to put my phone back to the way it was when I got it at the AT&T store. My phone model is SGH-i747 Galaxy S3 that came with JB 4.1.1 pre installed.
I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.
Click to expand...
Click to collapse
Out of curiosity, how did you finally manage to brick it?
Sent from my Nexus 7 using xda app-developers app
solution
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
There's another thread called stuck on boot screen with same issue. Had same issue with simular Rom had to boot in recovery and clear cache and user settings. And no longer an issue
Soft bricked...
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?
kinjo1023 said:
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?
Click to expand...
Click to collapse
I think I did someting like that too nd now I cant install any ROM and TWRP complains that I have no OS inside the phone.I tried modifying the assert-script file but it then eventually ends up at STATUS 6 and not status 7 again.Pls and Pls help us
You have to be on twrp 2.7.x to install any kk ROMs.
Sent from my SGH-I747 using Tapatalk
Hello,
I have a Samsung galaxy s2 T-Mobile edition.
I had Dirt Unicorns 4.3 installed on it.
I wanted to try something different so I was going to try liquid smooth 4.4.2
so I did the usual way:
-Boot into recovery Cwm 6.0.4.3
-made backup
-Factory reset / erase data
-wipe cache
-Wipe dalvik
-then ran Dark side super wipe ( I searched the internet and concluded that this is were I went wrong)
-Installed gapps
-installed ROM
It was all going fine but when the ROM booted up it was really terrifying. The ROM keep freezing and didn't let me do anything. Didn't even have the soft keys on.
So then I said oh well the rom blows(it probably doesnt just with me) so then I felt a little better because of course I had a backup of DU.
So I turned off my phone booted into cwm. This time it said something about it couldn't load the last_log.
Then I went to restore and tried to restore my backup.
All didn't go as planned, it moved system then data but when it went to .android_secure it immediately went to mounting sdcard0 and froze there.
so I let it stay there for a good 10min and nothing. So I held down my power button and it shut off. Turned it on it would go to a boot loop then just stay in the endless boot screen.
So after I felt really sad and down I tried to look up some stuff on my kindle about the problem.
Some people said it was cuz cwm 6.0 doesn't like darkside. It will do bad things so I was screwed.
then I read that it is a cache problem. So since the backups do the system and data I tried to do an advanced restore of just the cache. Long and behold it stayed frozen for a good 20m.
So then I tried a bunch of things trying to factory reset it can't format cache I tried to just for format the cache. nope. I tried to restore the backup a couple of times. I had another backup from awhile back of DU but some result. Then alittle bit of glory.
I had a backup of a while back. It was the jedi mind trick x4 ics. I restored that and oh man i was happy. It booted up fine and dandy and i have a decent "working" phone. It still has problems like when you lock the screen it doesnt turn off, just not interactive. and once i lock it the soft keys go crap and dont work(got button savior). So i thought well if this rom worked maybe the cwm is fixed. I tried to boot into the cwm through the power menu of the rom and it just froze while turning off. Held the power button then booted into recovery and the blue options line didnt come up so then i rebooted again and this time didnt let go of the volume buttons when the background came on. Thankfully they came on.
SO... i tried to run my backup of DU again and nope so then i repeated to go back to jedi mind trick cuz i need a working phone.
What im trying to solve is can i go back to DU working perfectly fine.
also i have tryed mostly everything in recovery But post as much help as you can and ill get back to you.
--
I also have been doing some research about the problem i had. Lots of other people had it but not really a solution.
I have kinda concluded on a solution in mind.
Heres the big question:
Can i unroot my phone and put the original firmware and stuff. Then just reroot and put a rom?
Is there a way to solve this problem?
Sorry for the big topic but i am really stressing because its a really good phone and i dont want to go to a crappy backup.
Thank you if you can help!
Lejojaluel said:
Heres the big question:
Can i unroot my phone and put the original firmware and stuff. Then just reroot and put a rom?
Click to expand...
Click to collapse
I had a similar issue flashing a new ROM and I had to unroot my phone as well. This was the guide I used: http://galaxys2root.com/t-mobile-ga...-to-ics-stock-on-t-mobile-galaxy-s2-sgh-t989/
After this you may want to upgrade to the latest firmware by using Kies, and then try your hand at re-rooting and putting another ROM.
Hope it works out for you. :highfive: :fingers-crossed:
Don't know about the rest of your post because I don't have experience with that ROM.
francoisdepaule said:
I had a similar issue flashing a new ROM and I had to unroot my phone as well. This was the guide I used: http://galaxys2root.com/t-mobile-ga...-to-ics-stock-on-t-mobile-galaxy-s2-sgh-t989/
After this you may want to upgrade to the latest firmware by using Kies, and then try your hand at re-rooting and putting another ROM.
Hope it works out for you. :highfive: :fingers-crossed:
Don't know about the rest of your post because I don't have experience with that ROM.
Click to expand...
Click to collapse
use that link , heres updated tar and odin
https://www.dropbox.com/s/2f0qpol7boj2jez/Odin3_v3.04.zip
https://www.dropbox.com/s/vxapb57yeuk60ud/T989UVMC6_T989TMBMC6_TMB.zip