[SOLVED] [Q] Stable CM7.1 Fails - AT&T Samsung Galaxy S II SGH-I777

Hey guys. I've been an Android & XDA user for a while now, so this question shouldn't be about a nooby-sitiuation.
My friend bought an AT&T Samsung Galaxy SII (SGH-i777) this week. I've been trying to flash CM7 ever since. I got the rooting done, the properly recovery (with no signature / "abort" problems)
The rom seems to keep bricking the phone. Its simply unflashable. I seen tons of people on XDA who got it to work, with barely any serious problems. I troubleshooted the problem myself, and its simply just the CM7 roms. I would do a full wipe, and then install the rom like I would on my other Android phones, and the installation is successful. When it boots, it gets stuck on the Galaxy SII boot screen (not the splash/boot animation screen) and it would stay on it with a yellow warning triangle on the bottom.
I tried flashing other roms, like Cognition X2, and they worked. Its just CM7 on this phone... which is odd because CM7 is usually stable (nightlies aside.) Especially since the 7.1 stable version was recently released. Anyone can help me get the rom up and going? Would be highly appreciated.

did you try to wipe dalvick cashe as well when you wiped data?

I just flashed it tonight myself and all I did was reboot into CWM and did a Wipe data/factory reset and then Wipe cache partition. After doing that, I simply flashed the cm7 zip file that was loaded on my internal sd. Rebooted and no problems.

I didn't have ANH ISSUES installing it but I know I read that some.people bad to flash it twice initially. So flash it, then when it goes back to the recovery screen flash it a second time. I also remember users on the international SGS2 bad to do the same thing. Most have no issues but I think they found that it depends on what you used to root your phone (on the SGS2 internationals) and I THINK some had to do the same here. Try it and if it works just hit the thanks button.
Sent from My KickAss CM7 Galaxy S2

if you flash it and get stuck in a bootloop, just pull the battery, and 3-finger back into recovery to flash the rom again.
keep doing this until you get it up and running - took me a few times, including a couple of battery pulls.

How do you boot into recovery? I know On the SGH-i777 you have to hold the Vol down+back+power to get to the Download mode, but I tried everything to get to the recovery itself.

Boobie Watcher said:
did you try to wipe dalvick cashe as well when you wiped data?
Click to expand...
Click to collapse
Yes. I've flashed many roms before, this seems to be the only one I had ever seen a problem with.

mfpearson said:
if you flash it and get stuck in a bootloop, just pull the battery, and 3-finger back into recovery to flash the rom again.
keep doing this until you get it up and running - took me a few times, including a couple of battery pulls.
Click to expand...
Click to collapse
Word.
Edit: To boot into recovery vol up+vol down+power

Had the same problem. Read somewhere to install the ROM twice in a row in CWM without rebooting inbetween. Worked like a charm.

Thanks for the feedback guys. I'll try this in the morning once I get my hands on the phone again.

Saw this type of behaviour on occasion with cm7 on my aria. Sometimes caused by a bad download of the rom. Did you verify md5s ?
Sent from my SAMSUNG-SGH-I777 using Tapatalk

Don't forget to do a master data clear /reset before trying to boot the new CM7 rom for the first time - clear out the old stuff. Works perfectly here.
Sent from my SGH-I777 using xda premium

I'm having the same issue. I'm getting signature errors when trying to flashCM7.1 stable. I've downloaded it two times now with the same problem. My question is, I'm trying to flash from on the phone itself, storing the zip in the download dir on the phone as I don't have an sd card. Will this even work? I've tried looking around and all I can find is flashing from an sd card. I can get one, I just haven't yet.

squigge said:
I'm having the same issue. I'm getting signature errors when trying to flashCM7.1 stable. I've downloaded it two times now with the same problem. My question is, I'm trying to flash from on the phone itself, storing the zip in the download dir on the phone as I don't have an sd card. Will this even work? I've tried looking around and all I can find is flashing from an sd card. I can get one, I just haven't yet.
Click to expand...
Click to collapse
That's the way I did it. Put the update in the same folder on the internal SD card. I can't even access my external SD card from CWM.
Sent from my SGH-I777 using xda premium

Hmm, I'm not sure what I'm doing wrong then. I did a factory reset, and wiped the cache and get the same thing. I know it wiped because now I have nothing setup on the phone when I boot normally. Suggestions?

Quit downloading the CM7 builds for the International Galaxy S II. They will NOT work. That is why it fails. Look for the Galaxys2ATT build.
Sent from my SGH-I777 using xda premium

I got the build by going to the cm7 website, looking by device, finding the galaxy s 2 and grabbing the stable one. So perhaps that is the incorrect one and I'll look closer for one that has att in it, whenever the site isn't going up and down. They seem to be having issues today.

Make sure you're installing the version located in this thread...
http://forum.xda-developers.com/showthread.php?t=1297568
Specifically this link

Double flash made it work. Thanks guys. + thanks for telling me how to boot into recovery lol. Great rom.

Sorry for the newb issues, it was the wrong version. I got the att version from the thread previously mentioned and that worked perfectly. Thanks!

Related

[Solved] CM9 Bootloop (Android Apps Update then back to logo)

Okay I have been trying to get a CM9 rom to boot on my Atrix for about a week now. I am coming from Nottachtrix 1.3.1 on radio 37p with faux GB24 kernel. My bootloader is unlocked and I perform all necessary wipes before install. The furthest I have gotten any of the CM9 roms to boot is the screen that states Android Apps(or something) updateing. It then states starting system and boots back to the booting logo. I have tried fastboot -w. Formating data, cache, system, osh, pre install in mounts storage menu, and clearing both caches before and after install and I get the same results. This only happens with CM9 roms. I cannot get the CNA, Jokers, Turls, or Atrix tablet past the screen stated. I have tried with the latest rom racer from http://forum.xda-developers.com/showthread.php?t=1204500 and both recovery and touch recovery from rom manager and I get the same results. I have posted my issue in the dev section, but decided this was better as I did not want to clutter up the dev forum with my problems. Could it just be my Atrix or would the 37p radio have something to do with the bootlooping issue. Any help would be very much appreciated.
For some odd reason I decided to pull my external SD card before boot, and freaking BOOM BANG POW NO BOOTLOOP!
htcslic said:
Okay I have been trying to get a CM9 rom to boot on my Atrix for about a week now. I am coming from Nottachtrix 1.3.1 on radio 37p with faux GB24 kernel. My bootloader is unlocked and I perform all necessary wipes before install. The furthest I have gotten any of the CM9 roms to boot is the screen that states Android Apps(or something) updateing. It then states starting system and boots back to the booting logo. I have tried fastboot -w. Formating data, cache, system, osh, pre install in mounts storage menu, and clearing both caches before and after install and I get the same results. This only happens with CM9 roms. I cannot get the CNA, Jokers, Turls, or Atrix tablet past the screen stated. I have tried with the latest rom racer from http://forum.xda-developers.com/showthread.php?t=1204500 and both recovery and touch recovery from rom manager and I get the same results. I have posted my issue in the dev section, but decided this was better as I did not want to clutter up the dev forum with my problems. Could it just be my Atrix or would the 37p radio have something to do with the bootlooping issue. Any help would be very much appreciated.
Click to expand...
Click to collapse
Did you flash twice ?
Sent from my MB860 using XDA
I believe the problem is with the radio, I had this issue (on stock radio), then I upgraded to the newest CM9 Kang (0.4.4) and it went away. I then flashed the 37p radio in an attempt to fix a problem I've been having with my WiFi and bluetooth (they both don't work and cause reboots, I assume now it's a hardware problem) and the boot loop came back. I'm gonna try flashing some other radios to see if that works.
Yes flashed twice to no avail. Gonna try the 36p radio and stock to see if that fixes my issue.
Sent from my Wettest Dream Atrix!
giqbal said:
Did you flash twice ?
Sent from my MB860 using XDA
Click to expand...
Click to collapse
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
CaelanT said:
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Trust me, the CM9 kang (not turl's version, haven't tried that) didn't work unless you flashed it twice up to version 0.4.2 (I skipped 0.4.3 and installed 0.4.4 straight without wiping and only flashed once and it worked, so it's possible they fixed the bug). I don't think anyone knows why, but it's been confirmed many times.
CaelanT said:
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
That is what I am hoping, but I have tried every procedure I could find within the forums. Your start to finish is gonna be my last hope.
So I followed the same steps I use for other roms and managed to get this one working http://forum.xda-developers.com/showthread.php?t=1580449
Hey CaelanT any luck on getting me a step by step.
hitmannumber47 said:
Trust me, the CM9 kang (not turl's version, haven't tried that) didn't work unless you flashed it twice up to version 0.4.2 (I skipped 0.4.3 and installed 0.4.4 straight without wiping and only flashed once and it worked, so it's possible they fixed the bug). I don't think anyone knows why, but it's been confirmed many times.
Click to expand...
Click to collapse
Haven't had to do that with jokersax, turl, or CNA versions.
---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------
htcslic said:
Hey CaelanT any luck on getting me a step by step.
Click to expand...
Click to collapse
Thanks for reminding me. Will get something to you here in a few!
<edit> Check your messages!
Gonna give it a shot soon as I get off work.
EDIT:
Unfortunately that was a no go as well. Followed everything to a tee and tried different kernels. I can only get the AOKP rom to boot, but its is currently without USB storage. Does anyone know a difference in the roms that would cause my Atrix to boot on one and not the other. I can also manage to get the MIUI to boot.
htcslic said:
Gonna give it a shot soon as I get off work.
EDIT:
Unfortunately that was a no go as well. Followed everything to a tee and tried different kernels. I can only get the AOKP rom to boot, but its is currently without USB storage. Does anyone know a difference in the roms that would cause my Atrix to boot on one and not the other. I can also manage to get the MIUI to boot.
Click to expand...
Click to collapse
I think something is going on with the kernel. You may have a bad processor. That's where my train of thought is right now. Sorry I couldn't get you up and running!
CaelanT said:
I think something is going on with the kernel. You may have a bad processor. That's where my train of thought is right now. Sorry I couldn't get you up and running!
Click to expand...
Click to collapse
Thanks for all you help. Finally got it to boot by removing external sd card.
[EDIT] Not sure but I believe the problem I had with m external sd is I still had an ext4 primary partition on it from when I was using Webtop2SD. Copying everything over to pc now and reformating external to see if my assumption is correct.
Looks like the ext4 partition on as was the culprit.
Sent from my Flipping ArtixTab!

Problems with most ROMS

Alright, we will start with a story - I am a fairly experienced root user. I had a fascinate, droid x, and now I have a thunderbolt. I had all three rooted and never had problems until now.
I have root access as well as a custom ROM on my thunderbolt. (I am currently using liquid 3.2).
The problem is that when I try to flash any other rom (I tried two: CM7.2 by ThunderShed and Infected by Virus) they do not work at all. I flash data, davik, and all that stuff. Infected gets stuck on HTC logo and CM7 gets further but freezes on startup after initial setup shows up.
My friend recomended flashing all different radios and I did that, but still having an issue. (I have 1.48.... and 0.0178... on now).
A few things.....check the md5 when you download. Wiping........wipe data/factory reset, then wipe cache, then go advanced and wipe dalvik cache, then go format/mount and format /system. Then install the .zip. If that doesn't do it, I have no idea, never had a problem flashing ROMs, only have problems once I start messing with them on my own.
I had to change to different recovery
Sent from my ADR6400L using xda premium
First, the roms do flash - just not boot up after. Both go through the process fairly well. Like I said - the only that actually works is Liquid 3.2, both Infected and CM 7.2 flash just get stuck at a different stage when booting up.
I'm going to download yet another rom and see whether that does it.
The recovery that I have is 5.0.2.1. I was going to install touch recovery and see if that was more reliable. I'll post later and see whether it was just the two roms possibly being bad (both downloaded from RootzWiki and not XDA).
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Try flashing a stock kernel first.
I also had the droid, droidX, droidx2, incredible2, thunderbolt, and now the galaxy tab. Also fairly familiar with rooting and flashing, and I had the same problem and couldn't figure it out. My clockwork was out of date. Updated, and everything was right in the world again. Check your Recovery. I didn't think if the update during flash took that it was my recovery but I was wrong.
flashing problem...
did you make sure usb debugging is on, and allow mock locations and non market downloads, and try deleting the current infected rom and re-download it just to make sure it was a clean download...i love the infected roms, especially eternity with darkhorsetheme. if that doesn't do it idk man. best of luck and try to get a hold of a developer maybe
Thank you guys!
Alright, so first off - I made sure my recovery was up to date.
I did wipe format /system and that caused infected to load, but after about an hour of using it - it froze and then when I pulled the battery, it wouldn't go past HTC logo.
I did load CM 7.1 and that works well.
I'll keep digging at it and see if I can figure it out. Thank you everyone!
Did you ever find a solution? I am having the same problem. I have tried 3 roms. It starts the boot screen and then after a minute it reboots into recovery.
It's the recovery folks.
Cwm = fail
4ext = win
donnyp1 said:
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
Using super wipe fixed this issue for me. Even after triple wiping dalvik didn't work, super wipe did. :good:

[Q] TWRP 2.4.4.x Boot Loop?

Has anyone else had a boot loop problem with the new V of TWRP?? I'm running SOAv3 ROM and had ZERO problems, upgraded my twrp and had about a dozen restarts and freezes and then when I tried to boot into recovery, it boot looped. Fixed it with ODIN, then tried installing it fresh, and got the same thing. Went back to my older version and things are fine once again just wondered if this is isolated or just a known bug??
Yes its a know issue right now go back to the previous working version of twrp and wait for it to get fixed.Also be sure to check big Biff's twrp page before trying to update again to make sure everything is good.
Sent from my SGH-I717 using xda premium
Just update from Padawan V8 to SOA build 3. Was skeptical for a day or so but finally did it last night. Was just about to update to the New TWRP, thank fully I read through all those pages before I did, I usually don't. Saved me a head ache except I forgot to wipe cache's before installing the GAPPS, going to have to re-do that I believe to get the new camera functions from what I've read.
Demmonnixx said:
Just update from Padawan V8 to SOA build 3. Was skeptical for a day or so but finally did it last night. Was just about to update to the New TWRP, thank fully I read through all those pages before I did, I usually don't. Saved me a head ache except I forgot to wipe cache's before installing the GAPPS, going to have to re-do that I believe to get the new camera functions from what I've read.
Click to expand...
Click to collapse
you are correct Sir.....wipe caches and re-flash gapps.....g
psycoartwork said:
Has anyone else had a boot loop problem with the new V of TWRP?? I'm running SOAv3 ROM and had ZERO problems, upgraded my twrp and had about a dozen restarts and freezes and then when I tried to boot into recovery, it boot looped. Fixed it with ODIN, then tried installing it fresh, and got the same thing. Went back to my older version and things are fine once again just wondered if this is isolated or just a known bug??
Click to expand...
Click to collapse
How did you fix with odin? I can't get mine into the download mode to connect to odin. it just keeps boot looping?
whitebrw said:
How did you fix with odin? I can't get mine into the download mode to connect to odin. it just keeps boot looping?
Click to expand...
Click to collapse
Hold volume down and power ...it will go into download mode
Sent from my SGH-I717 using xda app-developers app
thanks but no thanks, when i do that it does the same thing as any other way of starting, just loops.
check out my post if you want.
http://forum.xda-developers.com/showthread.php?t=2202663

[Q] Issues with booting and /data corruption

I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
edit: See my post here for details on what I've found so far, I may have fixed the problem but needs more testing http://forum.xda-developers.com/showthread.php?t=2397438&page=2
TWRP!!!!
SellswordShev said:
I've had this 4-5 times now, with various ROMs, tried CM10.1, 10.2 most recently. Basically the phone randomly stops booting, I can get to the recovery fine, but booting to system gets stuck on the Galaxy S4 Logo screen. Tried dalvik / cache wipes, permission fix, nothing helps.
Firstly, unless I completely wipe data (full wipe including /data/media), I can't seem to be able to install a new ROM. If I dirty flash everything works fine, but if I do a factory reset, I will get stuck on the logo at boot. Then even after I have successfully installed a ROM, I will sometimes randomly get stuck on reboots, and nothing but another full wipe will fix this. Is this an issue with the TWRP recovery? or is my internal memory fudged and getting corrupt ?
Click to expand...
Click to collapse
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
thepianoman77 said:
I'm having the same [email protected]#$%^& problem!!!! you're using TWRP aren't you?
i finished reading your post after I was done and saw that you ARE using TWRP...
Click to expand...
Click to collapse
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
SellswordShev said:
yep I was on TWRP 2.5.0.2, I just read that its got some stability problems with /data, just flashed v2.6 hopefully this fixes it
Click to expand...
Click to collapse
oh dude.... I was on v2.6... I think we have an issue.
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
hexitnow said:
That is why I use cwm. Been using it for 3+ years on 4 different devices. Never have I had one problem with it.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
i had a very bad experience with CWM... never using it again man.... no way.
thepianoman77 said:
i had a very bad experience with CWM... never using it again man.... no way.
Click to expand...
Click to collapse
Lol ok :thumbup:
Sent from my SCH-I545 using Tapatalk 2
I've been using TWRP too. I panicked last night when I couldn't boot at all. I couldn't even get to recovery. I then tried the no wipe odin without luck. I finally got the stock odin image to work but I've been having serious issues with booting on this phone since I got it this weekend and it could be TWRP I suppose. I was using it on my note 2 with no issues. Very strange. I'm back to stock and running fine now.
Sent from my SCH-I545 using xda premium
Still having odd issues with TWRP after updating to 2.6, getting stuck on boot as before, and sometimes flashing a ROM will just fail and the data partition becomes read only, and I can't push anything to it till I reformat /data.
Going to try CWM today, really hope this is just a recovery issue. Are there any tests to check the health of on board memory? I am really hoping I don't have bad hardware here.
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
ruffneckZeVo said:
Im having the same issue just made a thread fir it guess I will delete since I found this. Hope someone figures it out. What root/ recovery method did you all use. Was it the auto script?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Root / recovery methods will be the same for everyone, regardless of what guide / thread you followed, in the end you will have a loki-patched recovery and kernel, as thats the only way to run unsigned images on these phones. Whats relevant here is which recovery and kernel you are using, as these are the only 2 things that could effect errors in the boot logo state (aka freezes before the ROM boot animations kick in). Ive been looking through various ROM threads of people reporting this issue and its pretty widespread, and usually is linked to recoveries rather than ROMs. If you can post your recovery + ROM here that would be helpful. Here is what I've done so far:
I was initially on TWRP 2.5.0.2, which had possible bugs that could corrupt /data, leading to failed flashes, and being unable to read/write from /data entirely (including /sdcard). After switching to 2.6.0.0 I was still getting stuck on the boot animation. (All of this running the CM10.2 ROM with the stock kernel here http://forum.xda-developers.com/showthread.php?t=2384470). Note I did not do a full wipe after switching to 2.6.0.0, so that recovery MAY still be ok if someone wants to test it out.
I am now running CWM (official installed off ROM Manager). After flashing this I did a full re-format (/system, /data (including /data/media), etc.). And so far I haven't had any problems, going to do some more fiddling / flashing tonight to try and see if its really fixed, but I know for sure that atleast the reboot bug is gone.
So my advice is to flash the official CWM recovery, do a full re-format using that recovery, and then re-install your ROM.
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Monkz said:
I had that same /data issue with TWRP. It worked perfect for a few months and then suddenly it happened. I enjoyed TWRP for the 10 minute backups and restores, but i'd rather put up with CWM's 30 minute backup and restores if that will mean it wont happen again. Currently running PhilZ Touch Recovery and its been perfect so far!
Click to expand...
Click to collapse
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
SellswordShev said:
Have you tried any 4.3 ROMs with the PhilZ recovery? There seem to be some issues there. Still that recovery may be a good solution for those on 4.2 having this problem. I'm gonna try and loki patch the official CWM touch tonight if I don't run into this bug again, using the volume buttons is so bloody painful lol.
Click to expand...
Click to collapse
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Monkz said:
None of my ROMs are 4.3, but i know the one i'm using is soon to be updated, so i will know if it works or not when it gets updated to 4.3. But no issues on 4.2.2 ROMS as of yet with PhilZ.
Click to expand...
Click to collapse
is PhilZ a recovery?
thepianoman77 said:
is PhilZ a recovery?
Click to expand...
Click to collapse
Yes its a custom build of CWM maintained by an xda dev here http://forum.xda-developers.com/showthread.php?t=2322675
Im still having the issue with philz. Everything was fine for the first 4-5 weeks. Now about every 3rd reboot or if battery dies I have to wipe data and nandroid. Im running stock with several tweaks. Going to try and odin restore to stock re root snd install cwm tonight and see if that helps will report back
Sent from my SCH-I545 using xda premium
Alright, I'm almost 99% sure this problem is gone after I switched to the official CWM. I've tried everything from restoring nandroids to flashing TWiz / AOSP 4.2 and 4.3 ROMs, everything boots and reboots and /data is no longer getting corrupt. I also loki patched the official CWM touch recovery (the one on their site is not patched), and flashed + used it successfully. Its pretty simple to do this, just follow the guide here: https://github.com/djrbliss/loki and use this recovery: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.2-jfltevzw.img
The only issue I've been having is that when I reboot to recovery, it sometimes gets stuck and I have to do a battery pull and go back into recovery.
Sent from my SCH-I545 using Tapatalk 4
I'm having the same issue on TWRP 2.6. Tried with multiple ROMs. Everytime I reboot I have to format /Data. So frustrating. I will try CWM now.

Not sure what's happening. (Sort of urgent!)

Well let me explain my predicament. The other day I flash somex's something explosive rom after a wipe of the everything I need to wipe ( Data,Cache,Davlik) When it was finished flashing I got to rebooting. I ended up with a blank, yet illuminated screen ( if that makes sense) I waited about 20 minutes. After coming to the conclusion that the ROM doesn't work I did another wupe of everything needed. Then i flashed JoseGalre's ROM since it has aroma it told me that it had an error and coundln't finsih the instalation. I wiped again and reflashed, same error. I wanted to see what would happen if it let it boot up w/o recovery and it ended up in a boot loop. I tried to go back to 4ext and it seemed to load up just fine but half way through the startup it ends up back in the bootloop. I ran Hasoon's all in one kit and flashed TWRP and it worked just fine until I flash a rom. It seemed to be working just fine then it suddenly crashes and we're back in the loop. I've been trying to fix for the last few days but to no avail. I marked the title as urgent because my parents are going out of town for the weekend and I really need a phone. They havn't a clue that it doesn't work becausse they get home before me. Any help would be appreciated a great deal.
I've had something similar happen and freaked out my phone was down for half a day.
Try booting into the boot loader by holding vol down and power boot into recovery, wipe everything then format everything except SD card and try restoring a backup. Hopefully you made one or two in the past.
Sent from my HTC Amaze 4G running Evervolv jellybean 4.3
Illstatic said:
Well let me explain my predicament. The other day I flash somex's something explosive rom after a wipe of the everything I need to wipe ( Data,Cache,Davlik) When it was finished flashing I got to rebooting. I ended up with a blank, yet illuminated screen ( if that makes sense) I waited about 20 minutes. After coming to the conclusion that the ROM doesn't work I did another wupe of everything needed. Then i flashed JoseGalre's ROM since it has aroma it told me that it had an error and coundln't finsih the instalation. I wiped again and reflashed, same error. I wanted to see what would happen if it let it boot up w/o recovery and it ended up in a boot loop. I tried to go back to 4ext and it seemed to load up just fine but half way through the startup it ends up back in the bootloop. I ran Hasoon's all in one kit and flashed TWRP and it worked just fine until I flash a rom. It seemed to be working just fine then it suddenly crashes and we're back in the loop. I've been trying to fix for the last few days but to no avail. I marked the title as urgent because my parents are going out of town for the weekend and I really need a phone. They havn't a clue that it doesn't work becausse they get home before me. Any help would be appreciated a great deal.
Click to expand...
Click to collapse
I don't think you wiped properly. You needed to format ALL PARTITIONS. I can't stress that enough lol.
Edit: Go into bootloader first. Hold volume down then hold power as well. Choose recovery and format all partitions. If that works you're good! :thumbup:
Use the toolkit and flash 4ext. And make sure whenever you flash Roms that you format all partitions.
If that doesn't work you need to flash a RUU, get it back to stock, it will still retain S OF. Then flash 4ext again. Your problems should be fixed for sure if my first method doesn't work.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hey guys it completly out of the question to format my internal storage so keep that in mind
GB or IC RUU and which one?
You don't have to format internal storage just data, cache, system, and boot
Sent from my HTC Amaze 4G running CyanogenMod 10.1
Illstatic said:
Hey guys it completly out of the question to format my internal storage so keep that in mind
GB or IC RUU and which one?
Click to expand...
Click to collapse
Just choose format all partitions.
If you want to use a ruu use the T-Mobile ICS RUU.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So i changed the name of the RUU i download to PH85img.zip and use the all in one tool kit to flash it. The black htc loading screen came up. I waited until it finished and then the bootloader came up with a list of things it head to unzip and then load. After all of that was finished it gave me an error. After reading a message that you should get an error ( i now realize this was at another stage) so i though nothing of it and rebooted. A black screen with 4 warning triangles came up. I let it load all day and when i got home i plugged it back in and I noticed it looked like it was unplugging after securing the charger in I came the conclusion that it wasn't holding a charge and dying on the battery. Normally I would leave it alone but when you plug in the charger it turns itself on. I've began living with the fact that my phone is bricked. But any help would be appreciated.
BTW is there a way to get data (music pictures contacts) that were saved on the internal storage?
Probably should have gone with full caps on the PH85IMG.zip
It's easier just to put the zip on your external sdcard and gone in to bootloader.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
Probably should have gone with full caps on the PH85IMG.zip
It's easier just to put the zip on your external sdcard and gone in to bootloader.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
So is there anything that I can do when I plug it in it wont boot or charge at all so am i truly bricked or is there still hope
Illstatic said:
So is there anything that I can do when I plug it in it wont boot or charge at all so am i truly bricked or is there still hope
Click to expand...
Click to collapse
Should be hope, check out the unbricking project...
http://forum.xda-developers.com/showthread.php?t=1627882:cowboy:

Categories

Resources