Ran Automatic Unlock V4.2 , phone was previously unlocked but a ATT Motorola update removed Root and Unlock, was hoping for the official ICS but since we were left high n dry read and read and chose CM-10-20121023-UNOFFICIAL-olympus.zip and gapps-jb-20121011-signed.zip for my installation files.
Performed back-up, formatted data/cache, factory reset and flashed files under advanced since was getting the Status 7 error and it was found in forums as the work around when this occurred.
Phone will only get to splash screen with Motorola Icon and the unlocked message, I can enter recovery, tried another factory reset, still hanging, phone seems warmer than usual in this hanging event.
Will try another round of steps mentioned above, but since cannot post in developer thread yet, posted here.
Any suggestions, will mark resolved if this passes, but thought some might be more verse in this process playing with dailies and whatnot...
thanks all for any useful suggestions...
Found my own solution below...:laugh:
Went into mounts and chose to format system-data-cache, reinstalled the 2 files, still hangs on boot...
Thought this would be painless, work will be rough up all night resolving this, any suggestions, load a different rom?
Tried to use the back-up, it failed....
Perhaps I need to keep updating and reach 10 posts so can actually ask in dev thread, only phone and have work in morning, should have done this on the weekend, will have to take a day off if can't get this bad boy back up, or take a hit and buy phone on craigslist or facebook, lol,, fun fun..
I ran a custom Rom on my other Atrix no issues, but onboard speaker was doa and had to use Bluetooth all the time and was hassle sleeping, replacement phone had 2.3.6 so was just being patient for the ICS so hadn't played with this one until tonight...
Solution
placed v5 of CW recovery into auto unlock folder, renaming the v4 to old and just changing the name of the v5 to the name of the v4 so I didn't have to edit the bat file, re-ran script, chose the option 6 I think it was for flashing recovery, it flashed the one I substituted into the folder, loaded the zip files fron SD card again and then joy, phone booted, loading apps, back to testing and hoping to love this JellyBean on my Atrix...
Related
Hey guys,
Not exactly what to make of this which is why I'm posting. Here's the run down. Started off running Scamble_v01.3[CM6.1.3] for quite some time with everything just fine. About 2 weeks back, decided it was finally time to step it up to a Gingerbread ROM, and went with Wolfbreak's. For the first week, everything ran perfectly fine. This past week, I started to have issues with it rebooting every time I would run an app. Finally, this morning, it rebooted, and then just as it would get to the lock screen, it would say formatting SD card and then reboot. It would continue to do this repeatedly. I tried reinstalling in xRecovery (mind you I did Factory Reset (Full wipe), Wipe Cache Partition, & Wipe Dalvik Cache as well).
With high hopes, I restarted it. Unfortunately, this didn't change anything. I took my microSD card out and put Wolfbreak's updated ROM on it which just came out in hopes that maybe the file was corrupted somehow, just to find that when I tried to install it through xRecovery it, gave me an error that it couldn't because the SD card was busy. Stated in his ROM even, it says that you need to backup the ROM just for this very reason, however the only backup I had was of Scamble_v01.3[CM6.1.3] since I found it pointless to try and back up a messed up ROM.
Not knowing what else to try, and knowing that that was the last stable state my x10 was in, I restored that. Once again, it did nothing as far as the boot loop. I've gotten to the point where I have used FlashTool to flash the Generic Gingerbread ROM which just as all the others, gets to the first screen (which asks me to choose a language) and then reboots.
I'm completely stuck here and can't think of what I may be missing here. Any help would be greatly appreciated.
downwardzspiral said:
Hey guys,
Not exactly what to make of this which is why I'm posting. Here's the run down. Started off running Scamble_v01.3[CM6.1.3] for quite some time with everything just fine. About 2 weeks back, decided it was finally time to step it up to a Gingerbread ROM, and went with Wolfbreak's. For the first week, everything ran perfectly fine. This past week, I started to have issues with it rebooting every time I would run an app. Finally, this morning, it rebooted, and then just as it would get to the lock screen, it would say formatting SD card and then reboot. It would continue to do this repeatedly. I tried reinstalling in xRecovery (mind you I did Factory Reset (Full wipe), Wipe Cache Partition, & Wipe Dalvik Cache as well).
With high hopes, I restarted it. Unfortunately, this didn't change anything. I took my microSD card out and put Wolfbreak's updated ROM on it which just came out in hopes that maybe the file was corrupted somehow, just to find that when I tried to install it through xRecovery it, gave me an error that it couldn't because the SD card was busy. Stated in his ROM even, it says that you need to backup the ROM just for this very reason, however the only backup I had was of Scamble_v01.3[CM6.1.3] since I found it pointless to try and back up a messed up ROM.
Not knowing what else to try, and knowing that that was the last stable state my x10 was in, I restored that. Once again, it did nothing as far as the boot loop. I've gotten to the point where I have used FlashTool to flash the Generic Gingerbread ROM which just as all the others, gets to the first screen (which asks me to choose a language) and then reboots.
I'm completely stuck here and can't think of what I may be missing here. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Maybe give flashtool a go, just flash one of the stock firmwares.
Already tried that. As stated before, it gets to the first screen which prompts me to chose a language, and then immediately reboots
Fellow XDAers,
I'm in dire straits for some assistance.
I've been a member for some time now, lurking here and there, contributing when I have something of value. I've been through several phones, with an EVO 4G being my latest acquisition. Once I left Sprint as my carrier (Monthly rates were just too high for my blood), I was left with a phone that I couldn't flash to another carrier worth my valuable dollars (yes I know I could flash to Cricket or Metro PCS but I've never been a fan of their service). So, I started reading this forum and may others in regards to rooting and flashing.
After accomplishing this and having a case of ORD, I finally settled on FreshROM.
It worked well and outside of the occasional lag, I was pretty happy with my setup. Then a friend of mine finally converted from the TP2 to the EVO 3D. After answering several of his questions about rooting and flashing, he made the leap and flashed InfectedROM w/ beats audio baked in.
Being an audiophile and music blogger, I was of course interested to see if there was a ROM available w/ beats in it for my device. I found this one HERE called BlazingROM and installed the file from the first D/L link using the normal SD card method and Clockwork.
I of course cleared the Dalvik and the other cache. I didn't make a backup of my FreshROM as I already had one on my SD Card and in Dropbox for safekeeping as well as a Stock Odexed backup just in case.
The ROM installed just fine and I was enjoying the different elements of it while re-installing my apps with Titanium Backup when, the ROM started giving me messages that I was running low on internal storage space. I stopped TB and started using Apps2SD to move what I'd installed so far to the card. I then went back to TB to finish but with every installation, I'd get the "Internal Memory Low" message again.
By this time, I was scratching my head. I mean, yes I do have 20 must have apps but with FreshROM and Apps2SD, I was able to have almost all of those apps on the SD card without any issue. Now with this BlazingROM, why would I be encountering this issue? I then noticed that this new ROM had some sort of baked in Task Manager, which was the process giving me the error messages. So I attempted to use it instead of A2SD to move anything I could to the card. After doing so, I once again went back to TB to finish but upon the first install, I got the error message again. By now, I'm getting a little pissed and I still haven't even tried out the beats audio part of the ROM yet.
So, I decided to go back to basics. I opened Clockwork and did a Dalvik wipe and a re-flash of the ROM. Once that finished, I re-booted the phone. It was to no avail, as the Task Manager happily told me my Internal Memory was still too low.
I kind of panicked, not really…but a little…but I kept my wits about me and quickly went back to the post I got the ROM from in search of answers. I scoured any and all related replies which the consensus of brought me to the conclusion that my SD card should be formatted and then partitioned to accommodate the BlazingROM’s internal memory quirk.
Having no need to ever do so before, I then asked Mr. Google how it is properly done. Of course searching there brought back many links and after reading the majority of them, I settled on the method that involved ditching Clockwork Mod for Amon Ra’s recovery as it had more necessary options to partition than CW. That accomplished, I then found a guide for the different sizes of partitions as well as a discussion on the difference between EXT2 and EXT3 as well as the pros and cons of upgrading from one to the other.
I opted to leave the swap size at 0 (zero) and go for a 512MB partition. Once that was done, I then once again went through the steps to get BlazingROM flashed and running and once again, the evil “Internal Memory Low” message laughed at my efforts.
Fine I thought, I'll just go back to my good old trusty FreshROM until I come across another one w/ beats audio and none of these memory issues. I turned off the device, went to the Bootloader, chose Recovery and from CW Recovery, wiped the Dalvik again and chose to install FreshROM from zip on SD card.
Everything was going fine. It installed and I chose to re-boot the phone. That's when tragedy struck.
When my phone attempted to start up, the normal Boot Screen I'd come to love, where if you have the volume up, you see a hybrid of Tux and Andy while being greeted with a stylized "FRESHHHHHHHH!!" became stuck in the dreaded Boot Loop.
Back I went to Mr. Google to get some answers. This time he directed me to posts from here at PPCG to XDA to Android Central and various others. Almost every post I read instructed me that a Boot Loop could easily be fixed by placing the PC36IMG on the roots of my card and allowing the Recovery to find it in the Bootloader. I did so but it didn’t seem to make any difference. The phone continued to loop.
I did a battery pull but this time when I went to the Bootloader, ensured that it was indeed finding the PC36IMG and re-booted, I ended up with the Black HTC screen with four exclamation marks in the corners.
I’d never seen this screen before…so now I’m really panicking.
Off I went again in search for a solution. This time, I came across posts at all of the sites mentioned before but with a different solution involving the use of an RUU to take the phone back to it’s out of the box stock ROM state. Fine I thought. The phone will still be S-Off and I’ve got everything backed up on TB and Dropbox, it won’t be hard to get it back to where it was.
After checking the posting dates to ensure I was getting fresh info and links, I ended up at Shipped-ROMS. I D/Led what appeared to be the latest one and most recommended (RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe) to remedy my issue along with some instructions in a Word Doc regarding it as well that I found on another site. I even followed another post that added that I should install HTC Sync in order to have the right drivers on my PC for the RUU to work properly.
Long story short, after trying 10 different RUU’s as well as installing HTC Sync, uninstalling Sync and installing different HBoot drivers (2.10, 2.02, etc.) in all possible combinations, the only thing I’ve managed to do is end up with my phone still showing a Black HTC four exclamation mark screen. The only time the screen is different is when the RUU fails (either due to Error 152, Error 238 or Error 330) and I unplug the USB cable. The screen then shows an RUU Bootloader with these results:
SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.0808
Mar 30 2010, 11:24:04
RUU
Parsing ….[downloading ZIP]
[1] RADIO_V2 -OK
[2] SPLASH -Fail-PU
[3] RECOVERY -Fail-PU
[4] WIMAX -Fail-PU
[5] USERDATA -Fail-PU
[6] BOOTLOADER -Fail-PU
[7] SYSTEM -Fail-PU
[8] BOOT -Fail-PU
Partition update fail!
Update Fail!
For some reason, each and every RUU gets up to around 32% to 40% and begins to show signs of failing while Updating User Data.
I’m reluctantly conceding defeat on this, as I have no clue as to what to do now. I’ve even gone as far as downloading Android SDK to try and figure out how to push the RUU or some kind of fix through ABD Shell.
If anyone has anything constructive that could help, I’d appreciate it greatly.
Wow. sorry my friend. I feel your pain as something similar happened to me with a HD2 once..my nand had gone bad. it seems you have pretty much tried everything. only recommendation I have is if you are still able to flash stuff try older version radios (downgrade radios first) before you try to RUU and don't neccesarily go for latest RUU you find. also leave out your SD card while trying the RUU. - fully format your SD card is also another thing I did not see in your long list of things you already tried? if you can't flash thru recovery (or maybe even your recovery somehow is messed up!?) try this new tool called Android Flasher I just saw someone has released on XDA. looks very good but I have personally not tested it yet. http://forum.xda-developers.com/showthread.php?p=18279765#post18279765
good luck maybe one of these combinations might work.
Gonna try and see what this can do to help later this evening. I appreciate the help and will report back what happens.
I recently installed the nightly build of ICS on my samsung vibrant. Today the phone had a error that said encryption cannot be completed phone must be erased. I let it do a factory reset . Then I got stuck in a endless boot cycle showing the vibrant logo and then the cynogen guy for a few seconds then reboot. I could still access the recovery menu but it refused to flash any roms I threw at it. I downloaded and ran odin 1 click recovery and it changed my tmobile phone to a att phone. And it lost the recovery mode. It just shows att screen first then samsung vibrant second and just reboots. I can still get into download mode and flash roms using odin 3 but no matter what rom I select or if I choose repartion or not the flash will go through successfully but then the phone reboots into same problem as before. I suspect the recovery files are gone since no button combination anymore gets me into recovery. Is there anything else I can do?
Man I am having the exact same problem. I really hope someone can figure something out soon. Did yours randomly get that error? Or did you actually try to encrypt your phone?
Sounds like you used the wrong Odin 1 Click. If it installed Captivate bootloaders, that would cause a problem.
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
It just happened
It happened on its own. Was working fine all day walked in my house as as soon as it hit wifi it started going crazy. I had the data plan turned off months ago. Maybe theres something to it connecting up to the net. I have found out if you install your sim you get a reduced menu of recovery options but without sim it just constantly reboots. it only gives option of reboot, reinstall packages,delete all user data, delete cache data. If you try reinstalling the packages theres nothing there. Deleting caches made no differance. ADB does work and responds while in this lesser form of recovery is there a easy way to use adb to force a full system flash?
Thanks
That link was perfect had a link to eugenes no brick froyo rom which fixed my problem. Dloaded that used its pit and tar files and repartioned and im back to stock. Going back to team whiskeys mod. If all ICS roms has bugs like that is unusable.
bfranklin1986 said:
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Do you have access to BOTH your internal and external SD cards? The Encryption Bug is totally and completely random and does not discriminate. There is currently no known reason or solution. Several of us across a few different devices have been working on this for months.
Consider yourself luck if you have access to both SDs as you are the 2nd person to get in and out today. Many, many others have not been as fortunate.
If you could please pull up this thread and put as much information in there as possible, it would be greatly appreciated. Are you unlocked, what happened right before, what bootloaders are you on, what ROM were you trying to flash, what ROM did you end up getting booted,....those types of things. As much detail as you can muster together, after you catch your breath and relax a minute.
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Update
I think I might have pulled the trigger to quick. While the link above did give me Eugenes rom which at least got me out of the boot cycle both internal and external sd shows 0 and I am unable to load anything on either card. I have tried differant microsd cards all of them show the same thing. So eugenes rom got me working kind of but cant store anything at all. That sucks loved my vibrant and its almost out of contract and planned on using on prepay.
Agreed 100 %
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Moped_Ryder said:
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Click to expand...
Click to collapse
chickenmon said:
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Click to expand...
Click to collapse
I got tagged on a Nook Color with it. BUT, since the Nook Color has a feature that no others I think do (you can boot a ROM straight from an SD card and not mess with the oringinal OS at all), I was able to just pull my Microsd out and reformat it and then put CM7 on it for my wife.
So far from what I have seen and been working on:
Vibrant, Captivate, My wife's Nook Color, A few Transformers, SGSII,...
Anything I can do?
Anything I can do to get my partions right again? I can flash the twm 5.2.2 but none of the roms i throw at it including ics passion stays in a boot cycle. Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
chickenmon said:
... Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
Click to expand...
Click to collapse
You may want to bring up this issue directly in Merio90's thread. I believe Alex9090 went thru possibly similar issues and may be able to help you in that thread (unless she happens to pop in here).
I'm assuming you were trying to mount sdcard and emmc within recovery first (storage and mounts)? If you do have access to recovery again and can mount the external sdcard, maybe try repartitioning the card within recovery (using the parameters in Merio90's instructions)? Then transfer your rom zip and re-flash.
People have actually flashed Eugene's Froyo post-EU ... but without an ext sdcard. Quite an oddity. It's the only one (AFAIK) that'll fully boot up (even after losing int sdcard access due to EU) yet without an external sdcard in place.
Your assumptions are correct. I cannot mount emmc. I cannot flash any rom via 2.5 or 5.2 recovery only through odin and only eugenes rom still allows phone to boot but no mounting of internal or external sds. Ive spent about 3 days on this. There must be some hardcore adb commands to force a true factory reset partioning and all. Very annoying. Thanks for the help if I find any ways to fix it I will repost it here.
Might be bricked?
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Not related at all to my original problem.
tenantrep said:
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Click to expand...
Click to collapse
First of all, not to sound like a ****; but it's rude to hijack someone elses thread. You should've created your own thread for this.
Second; you might have fried your bootloader which in turn, yeah, that's bad and you might have bricked your phone.
Did you try to boot into recovery via the battery pull method. If not, try that and see how it works. I would link you to the instructions but I'm too lazy and tired right now to search for it and again, this is someone else's thread. Just do a search for it and you should find it.
If you need more help or guidance, create your own thread and start there.
Noticed your running Ice Cream Zenwich rc1.3. How do you like it. Ive installed slim 3 times today and twice I have gotten the encryption error within a hour. Needless to say not impressed major pain in the ass to have to do a million and half tricks with awm, adb, popping sd cards in and out etc.
Update
Also the current build of ics slim does not allow the imei information to be retrieved from sim for tmobile requiring a reflash of the modem. You have to download and install a new modem. I used csm5. The guide on the link in this post dow work but its a real pain and requires lots of trial and error. Wondering if google intentionally bricking these things knowing we all got gadget lust for the sIII now.
chickenmon said:
Noticed your running Ice Cream Zenwich rc1.3. How do you like it ...
Click to expand...
Click to collapse
ICZen_rc1.8.3 (AOKP #39, ICS 4.0.4) + subZero #144 (New Test Kernel just released in mr_pyscho's RootzWiki kernel thread) is Linaro infused ... and I've got to say the combo is THE fastest rom experience I've ever had on my Vibe. Whatever MP did in his new test kernel just blows the doors off the previous performance limits.
Btw .. you keep encountering EU again. Really odd unless possibly your external card wasn't partitioned correctly. Not a knock directly on you, but it is a common occurrence lately. FYI, I repartitioned mine directly from recovery.
Also ... Br1cK'd (ICZen) and mr_psycho (subZero) are aware of the EU situation and try to include safeguards in their builds. However, until we know the exact root cause of EU, we're all just shooting in the dark. Imo, it's at least comforting to use a rom & kernel where the dev's are at least mindful of EU.
It's quite a long story,but I'll try to keep it short, yet detailed.
I rooted my Samsung Galaxy S3 (SGH-T999) about two weeks ago. I made sure to practice the rooting process and read up on the dos' and don't-s' when it comes to rooting and installing custom Roms. A week ago I installed a custom Rom from Aokp known as "AICP (Android Ice Cold Project)." Everything was going good till yesterday when I saw that I was having some memory issues. My internal memory was quite full and I realized and understood that when I wipe--factor reset--my phone, that there is still some data that is left over. Now before I installed AICP I made a backup of the S3 stock Rom. When I seen that the internal memory was getting full I formatted the internal-SD in recovery mode (forgetting that the S3 backup was in it). I decided to, after formatting the internal-SD, try some new Roms. I followed the flashing instructions carefully as always. I went back to AICP and put the phone down for a bit. When I came back to use it, it was frozen. So I restated the phone and then I began getting a message that stated that "Unfortunately, the com.android.systemui (something regarding the task/notification bar) has stopped." I pressed okay but it kept popping up, and the home screen kept flashing. I could move around but only for 1sec before the message popped up. And when I cut the screen off it just froze. I did a factory reset, it didn't work; I reinstalled the Rom and other Roms, didn't work; I couldn't clear the system ui because the Roms didn't allow it. I've Youtubed and read everything, nothing. So I re-rooted my phone, didn't work. Now here is where the problem is. When I re-rooted my phone, it booted to AICP but the message still popped up. I tried to reinstall the Rom but it aborted the installation. I tried to install other Roms, same thing. Now the phone will only boot Recovery Mode and nothing else. I've been trying to flash the S3 4.3 Jelly Bean Stock Rom via Odin, but every website I go to ether doesn't have the file or it won't let me download the file. Now I did get one S3 Stock Rom, but I can't get the file to unzip . Does anyone have a solution to this weird problem... X( BECAUSE I CAN'T ANSWER THE PHONE IF MY GIRLFRIEND CALLS!!!!
DeathsSatellite said:
It's quite a long story,but I'll try to keep it short, yet detailed.
I rooted my Samsung Galaxy S3 (SGH-T999) about two weeks ago. I made sure to practice the rooting process and read up on the dos' and don't-s' when it comes to rooting and installing custom Roms. A week ago I installed a custom Rom from Aokp known as "AICP (Android Ice Cold Project)." Everything was going good till yesterday when I saw that I was having some memory issues. My internal memory was quite full and I realized and understood that when I wipe--factor reset--my phone, that there is still some data that is left over. Now before I installed AICP I made a backup of the S3 stock Rom. When I seen that the internal memory was getting full I formatted the internal-SD in recovery mode (forgetting that the S3 backup was in it). I decided to, after formatting the internal-SD, try some new Roms. I followed the flashing instructions carefully as always. I went back to AICP and put the phone down for a bit. When I came back to use it, it was frozen. So I restated the phone and then I began getting a message that stated that "Unfortunately, the com.android.systemui (something regarding the task/notification bar) has stopped." I pressed okay but it kept popping up, and the home screen kept flashing. I could move around but only for 1sec before the message popped up. And when I cut the screen off it just froze. I did a factory reset, it didn't work; I reinstalled the Rom and other Roms, didn't work; I couldn't clear the system ui because the Roms didn't allow it. I've Youtubed and read everything, nothing. So I re-rooted my phone, didn't work. Now here is where the problem is. When I re-rooted my phone, it booted to AICP but the message still popped up. I tried to reinstall the Rom but it aborted the installation. I tried to install other Roms, same thing. Now the phone will only boot Recovery Mode and nothing else. I've been trying to flash the S3 4.3 Jelly Bean Stock Rom via Odin, but every website I go to ether doesn't have the file or it won't let me download the file. Now I did get one S3 Stock Rom, but I can't get the file to unzip . Does anyone have a solution to this weird problem... X( BECAUSE I CAN'T ANSWER THE PHONE IF MY GIRLFRIEND CALLS!!!!
Click to expand...
Click to collapse
Wrong forum my friend.
DeathsSatellite said:
It's quite a long story,but I'll try to keep it short, yet detailed.
I rooted my Samsung Galaxy S3 (SGH-T999) about two weeks ago. I made sure to practice the rooting process and read up on the dos' and don't-s' when it comes to rooting and installing custom Roms. A week ago I installed a custom Rom from Aokp known as "AICP (Android Ice Cold Project)." Everything was going good till yesterday when I saw that I was having some memory issues. My internal memory was quite full and I realized and understood that when I wipe--factor reset--my phone, that there is still some data that is left over. Now before I installed AICP I made a backup of the S3 stock Rom. When I seen that the internal memory was getting full I formatted the internal-SD in recovery mode (forgetting that the S3 backup was in it). I decided to, after formatting the internal-SD, try some new Roms. I followed the flashing instructions carefully as always. I went back to AICP and put the phone down for a bit. When I came back to use it, it was frozen. So I restated the phone and then I began getting a message that stated that "Unfortunately, the com.android.systemui (something regarding the task/notification bar) has stopped." I pressed okay but it kept popping up, and the home screen kept flashing. I could move around but only for 1sec before the message popped up. And when I cut the screen off it just froze. I did a factory reset, it didn't work; I reinstalled the Rom and other Roms, didn't work; I couldn't clear the system ui because the Roms didn't allow it. I've Youtubed and read everything, nothing. So I re-rooted my phone, didn't work. Now here is where the problem is. When I re-rooted my phone, it booted to AICP but the message still popped up. I tried to reinstall the Rom but it aborted the installation. I tried to install other Roms, same thing. Now the phone will only boot Recovery Mode and nothing else. I've been trying to flash the S3 4.3 Jelly Bean Stock Rom via Odin, but every website I go to ether doesn't have the file or it won't let me download the file. Now I did get one S3 Stock Rom, but I can't get the file to unzip . Does anyone have a solution to this weird problem... X( BECAUSE I CAN'T ANSWER THE PHONE IF MY GIRLFRIEND CALLS!!!!
Click to expand...
Click to collapse
1. Flash this file: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2tmo/philz_touch_6.15.4-d2tmo.tar.md5 in odin3.09, uncheck autoreboot.
2. go to your recovery, select clean to install a new rom
3. download latest firmware (http://www.sammobile.com/firmwares/3/?download=26636) and install it in Odin3.09
4. reboot your phone.
See I figured that's what I needed to do. Just couldn't find a Rom to flash with Odin. I'll use this method right now.
Here's one of the problems I was having when it came to Odin and the Firmware. The website, "Sammobile," you sent me was one of the websites that I had the files I need, but the link you sent me to, which is the file I downloaded, didn't show up when I clicked AP/PDA in Odin and tried to mouth it. The .zip didn't show up and when I tried to unzip the T999UVUENC2 file, it stopped at
%63 and says:
! Read error in the file C:\Users\Mrs Woods\Downloads\T999UVUENC2_T999TMBENC2_TMB.zip
Data error (cyclic redundancy check).
! Not enough memory
What should I do?
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.