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
Related
First time I'm posting so hey.
I just bought a HTC Hero today and decided to load a custom ROM onto it.
I flashed it fine, and installed modaco earlier (file name: 2.8-update-hero-modacocustomrom-core-signed).
So when I powered it back on, it looked like it worked fine, but I must of went wrong somewhere.
The phone will boot up, stay on for like 5 seconds, and then restart. When it comes on, I can't do anything cause it freezes on the lock screen then just restarts.
I'm pretty sure I messed up by putting that ROM on a t-mobile UK Hero(which I unlocked). I aint sure as I'm only new to this.
Any advice on how to fix this?
did you do a phone wipe before installing the custom rom?
I formatted the SD card.... I think before I flashed it.
Then just put the ROM on the root of the SD card.
See it looked like it done everything fine with the ROM.
I held in the home/power buttons, loaded the boot menu.
I did a "Ndroid back up" (did I spell that right) - so I could restore in case something like this happened (which I did, since I need my phone lol), then picked "SD Choose", picked the modaco ROM and it seemed to install fine. Took a few minutes. Install complete. I rebooted the phone.
Then it loaded the normal boot screen, and would literally last only 1 second and freeze on the lock screen saying no signal, then it would reboot. And loop this pattern.
Neo-Dragon said:
I formatted the SD card.... I think before I flashed it.
Click to expand...
Click to collapse
A wipe has nothing to do with the SD card. It is essentially resetting your phones internal memory back to "factory" defaults. I take it you have a custom recovery image, as you mentioned making a Nandroid backup - you will find an option to wipe there.
Regards,
Dave
So if I wipe the phone before hand and then upgrade it should be fine?
If I do a nandroid back up, will I still be able to roll my phone back if it fails?
A wipe now may fix your problems with you needing to upgrade again.
My suggestion would be trying this first - if it doesn't help, restore your nandroid backup, wipe, and apply the new ROM again.
Regards,
Dave
Cheers mate.
After the wipe, I re-installed the ROM and it works perfect.
Thanks again.
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...
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....
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?
To make a long story as short as possible, Im on MDK bootloader and I was running stang5liter 5.0 with CWM recovery. I've been bored lately with my phone so I've been flashing a bunch of different roms trying to get the coolest touchwiz rom with most features while using up least amount of system memory as possible (obvioisly). Well I was messing around before attempting to flash Pheonix Rom (ported stang5liter) and I wiped factory reset, cleared cache, dalvik. Then I went into advanced, format system, and then I tried format (sd-ext) which I never have done before and really don't know what it does but figured what heck I'll try it since I've soft bricked this phone multiple times and am fluent at bringing it back to life again. So after I did format (sd-ext) I went to flash rom and clicked on Phoenix Rom zip which I had on my external sd card and pressed "yes flash rom" then CWM looked like it was about to flash but all of a sudden the screen went black and CWM came back to main menu with no flash. I had already wiped the phone so I couldn't reboot to previous system image and of course I didn't have a backup and now I couldn't get CWM to flash any of the rom zips I had on my sd card so I had to ODIN back the emergency sch-i545 mdk tar and everything in Odin seemed like it went just fine. Everything booted up and phone seemed like it was working fine, but. I have noticed big problems since then. 1st thing I noticed was phone getting really hot to the touch, then when I tried to turn it off it shuts down but back key lights and notification light stays on and it never does the final vibrate and turn all the way off, same thing when I try to reboot it just stays like that until I pull batery but it boots back up fine after that. Also I enabled developer options but when I go down and try to open the developer settings in the about phone menu my phone freezes and it will never open. Other little things happen to llike apps FC and sometimes when I open them its like I'm opening it for the first time again line there's no cache memory or something. Then I tried to root again and was successful with towel root and I installed SU and terminal emulator and attempted to flash CWM with loki patch and everything in terminal looks as if it's good and I actually got it to install but when I tried to flash Phoenix Rom again it did the same thing and had to run through the whole Odin process again and now I'm back to the same problems and I'm going crazy trying to find threads with similar problem but have not found anything really at all, can someone please help!