Related
I rooted my sister's phone, then installed launcher pro, and it bricked! (UGH!!!)
So I came here looking for rescue and did the Odin system restore steps. Like another poster there mentioned, it appeared to work, and everything seemed fine other than one critical component: it wouldn't sync at all with her google account!!! I've tried installing the clockworkmod, too, because that same poster said he got it to work by doing the clockworkmod reset. I can't get it to reboot into the clockworkmod recovery console, just the android one. How do I get to the clockworkmod console???
Remember that I have no market access until the google account syncs properly.
I did all the steps I could, but I still can't get the phone to sync with my sister's Google account. It locked up and perma-black screened after rooting and installing launcher pro, so I tried to use the backup from Odin to save it. Saved the phone. Seems to work. The verizon backup option successfully restores her contact info.
I can't get it to sync with her google account, and I am LOSING MY MIND because I have to leave early tomorrow morning, and I don't want to leave my sis. with a broken phone.
And where in the heck do you get the oft-mentioned "update.zip" file from???
HELP!!
SirKronan said:
I rooted my sister's phone, then installed launcher pro, and it bricked! (UGH!!!)
So I came here looking for rescue and did the Odin system restore steps. Like another poster there mentioned, it appeared to work, and everything seemed fine other than one critical component: it wouldn't sync at all with her google account!!! I've tried installing the clockworkmod, too, because that same poster said he got it to work by doing the clockworkmod reset. I can't get it to reboot into the clockworkmod recovery console, just the android one. How do I get to the clockworkmod console???
Remember that I have no market access until the google account syncs properly.
I did all the steps I could, but I still can't get the phone to sync with my sister's Google account. It locked up and perma-black screened after rooting and installing launcher pro, so I tried to use the backup from Odin to save it. Saved the phone. Seems to work. The verizon backup option successfully restores her contact info.
I can't get it to sync with her google account, and I am LOSING MY MIND because I have to leave early tomorrow morning, and I don't want to leave my sis. with a broken phone.
And where in the heck do you get the oft-mentioned "update.zip" file from???
HELP!!
Click to expand...
Click to collapse
Go into Privacy - Settings - and do the system reset / factory restore. That should allow you to re-synch with google.
namebrandon said:
Go into Privacy - Settings - and do the system reset / factory restore. That should allow you to re-synch with google.
Click to expand...
Click to collapse
Ok. Giving it a try right now.
What guide did you follow for Clockwork? I've seen a number of people with the missing update.zip file, and I cannot figure out how that is happening.
It's like 1 out of every 5 people have this problem, and I don't get it.
HOLY CRAP BATMAN.
You're a LIFESAVER. It worked. Hallelujah!!!!!
Thank you sooooo much!!!
No problemo.. Sat there for about 2 hours myself before I figured that one out.
namebrandon said:
What guide did you follow for Clockwork? I've seen a number of people with the missing update.zip file, and I cannot figure out how that is happening.
It's like 1 out of every 5 people have this problem, and I don't get it.
Click to expand...
Click to collapse
This one:
http://forum.xda-developers.com/showthread.php?t=788099
Did it carefully, step by step, as far as I can tell. Now I'm having trouble rooting the phone again after that factory reset. It pushes the files, resets the phone, then starts the rooting process ... then it says device disconnected, even though I see no signs that it is, and it still says on the screen that it is connected. I think I will try the long, manual rooting option next.
Ok, I successfully got it to root, but only by the slower manual method. I could never get the one click method to work again, even after multiple tries. It got all the way through most of the process but failed to install superuser.apk. Once that part was done, it's been working great so far. I hope. So far so good ....
Unfortunately I think you learned that the hard way..
Take your time, don't take shortcuts, don't make assumptions.
Most of the time the one-click solutions end up causing more problems than their worth.
I bet if you had to do that "long" process again, you could do it in ~5 minutes now.
Glad you got it all working.
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
I purchased an ASUS Transformer Prime TF201 in July last year from a guy on eBay. He unlocked it and rooted it and had ClockworkMod Recovery 5.8.2.0 (or something like that) on it. Was working great until about a month ago...
When I turned it on, it started updating my apps and whatnot, like it usually did. I don't know if it hit one it didn't like or if it was an OS update (I'm thinking the new JB update) but it rebooted the system. When it booted back up, all my apps were gone, the Google Play store was gone... everything vanished. I couldn't get onto the net, nothing. So I went to try and do a restore of a previous state. When I did, it booted me into CMR and stayed in a loop. I found out my OS was wiped from the system. There literally are NO FILES FOUND on this system.
I tried an adb push to move the files to the system to install a new OS, but no luck. I tried an adb install but I get a message saying AndroidManifest.xml is not found and I can't install. I can't get any files onto it nor can I get anything to install to it.
I tried to talk to ASUS for help, but my options with those @$$holes are either send it to them to be repaired or suffer the brick. I really need some help here! What do I do to fix this?
are you still able to get into recovery via down volume+power when the system is off
egyptian_rose said:
I purchased an ASUS Transformer Prime TF201 in July last year from a guy on eBay. He unlocked it and rooted it and had ClockworkMod Recovery 5.8.2.0 (or something like that) on it. Was working great until about a month ago...
When I turned it on, it started updating my apps and whatnot, like it usually did. I don't know if it hit one it didn't like or if it was an OS update (I'm thinking the new JB update) but it rebooted the system. When it booted back up, all my apps were gone, the Google Play store was gone... everything vanished. I couldn't get onto the net, nothing. So I went to try and do a restore of a previous state. When I did, it booted me into CMR and stayed in a loop. I found out my OS was wiped from the system. There literally are NO FILES FOUND on this system.
I tried an adb push to move the files to the system to install a new OS, but no luck. I tried an adb install but I get a message saying AndroidManifest.xml is not found and I can't install. I can't get any files onto it nor can I get anything to install to it.
I tried to talk to ASUS for help, but my options with those @$$holes are either send it to them to be repaired or suffer the brick. I really need some help here! What do I do to fix this?
Click to expand...
Click to collapse
Yeah, CMR is the only thing still on there, and its the only thing I can access or use. Everything on it comes back with "no files found" when I try to do anything like restore or factory reset or whatever. Can't seem to access any sd cards on it. Androwook prime is gone too, so I can't try to reinstall from that because of the data wipe/ factory reset. Basically, all I can do is access CMR's menus and stay in a boot loop.
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
boneyarsebogman said:
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
Click to expand...
Click to collapse
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
es0tericcha0s said:
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
Click to expand...
Click to collapse
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
es0tericcha0s said:
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
Click to expand...
Click to collapse
I've wiped the Caches and Dalvik Cache and can't seem to find "Fix Permissions". I did some searching and it seems this feature was removed from CWM? I'm running v6.0.3.7 of CMW.
When I try to format the system, it says
E:format_volume failed to unmount "/system"
Error formatting /system!
Weird, they did take it out. Koush said it was a placebo. Which normally I would take as law, if it weren't for many times I have ran fix permissions and it caused apps that were force closing to not force close anymore. But whatever, if you wanna try, flash this: http://db.tt/9aWdF8Rp. It'll either help fix something, or do nothing. Won't make it any worse. If it can't mount to format though, it's either or a bug with CWM for your device, or after factory reset, reboot recovery and try again. But you really don't want to wipe /system unless you have a nandroid or another rom on your storage that is accessible.
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
boneyarsebogman said:
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
Click to expand...
Click to collapse
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
es0tericcha0s said:
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
Click to expand...
Click to collapse
Mine is the P2-6011.
Swear if we get this working, never changing anything ever.
Yes, the bootloader is unlocked.
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
es0tericcha0s said:
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
Click to expand...
Click to collapse
If I ever meet you I definitely owe you a drink. Did exactly as you said and everything (from what I can tell) is working.
It's one of the things I love about Android phones - unless you do some serious damage to it physically, for the most part it is fixable.
So, thanks button isn't enough - you saved me giving up and buying a new phone
*Hi Five* Glad all is well!
But yea, I do this for a living. Seriously. Helping people on here is how I stay sharp. lol
getting a gateway 504 error from link to firmware, would love to get this update working as i keep getting a notification on phone saying update available but it wont work
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
Can you post the link of the CM 10.2 rom For huawei P2.
I search for a long long time. but still dosnt found a rom.
Thx
Sorry for digging this up but does someone have the stock ROM of the P2? Im stuck like the fella who started this thread and havent found the stock ROM anywhere.
Thanks for the attention.
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?