I've accidentally upgraded the superuser to 3.0 & now I can't revert it back to v2.3.6.2. Tried Formatting & installing the fresh rom again but still the superuser 3.0 stays there. Also tried installing v2.3.6.2 & shows that it's been successfully installed over 3.0. Runs perfectly but after a reboot, again v3.0 appears on homescreen. Can't get it out even after wiping everything . Please help!
What's wrong with SU 3.0?
It isn't fully compatible yet with cm7 or gingerbread.
http://androidsu.com/2011/09/initial-impressions-of-3-0/
Read the 4th point. Also experienced issues with some apps not working anymore just after that.
Thanks, m8
Worst case, re-flash CM7 again.
Tried re-flashing it many times but the superuser 3.0 was still there. And now I can't even boot to cm7 because I have restored my previous nand backup where I had the old superuser. It's keep on rebooting to CWR when I select reboot system. I thought restoring to previous backup will get the old superuser back. WTH
OMG. Now I can't even boot into CWR . I formatted the boot from CWR because nand restore was not helping & now even more worst, stuck at read forever screen. Also tried CWR using microsd but the same problem. It's getting even more worst. Please someone on earth help me.
Related
First of all i hope everyone is having a good day. So heres my problem. I have searched around the forum and i see people had problems with the looping Quitely Brilliant screen. The thing is i have no backup. I know huh? So this is what happened. Everything was perfect. I used cyanogenmod but soon after I tried installing evil d's 4g HD ROM. Right after, forsome reason, i formatted the sd card. I think under cyanogen it said the SD card was corrupt and it asked to format it which i did. So i wipe data/factory reset and installed evil d 4g HD rom. Its stuck overlooping at quietly brilliant now.
I have the latest clockwork installed. I think i had to downgrade to 2.5 maybe.
Any other suggestions please are greatly appreciated.
Ive tried...
Wipe data/factory reset
Wipe dalkin
Reflashed evil d rom.
Now im trying to find a way to downgrade clockwork without having the ability to get to main screen. Please help
If the "latest clockwork" is 3.0.0.5, it is for Gingerbread ROMs only. So reinstall CM7. If you don't have it any longer, you can move the .zip from your PC to the phone via clockworkmod recovery, mounting the SD to the USB under mounts and storage.
For Froyo-based ROMs, you must use clockworkmod recovery 2.5.1.2, or the extra-special-built-just-for-us-by-option94-and-unique-for-MT4G "3.0.0.6" version, which can manage both Froyo and Gingerbread versions of Android.
nice! i actually was about to reply to my own post about the solution i found. i did exactly what you said. appreciate it!
Something got messed up when I tried to flash my acer a500 from a rooted version of 3.1. One problem I have (and I admit it was my fault) is I did not move my backed up ROM to my external card - so I don't have anything to restore.
My device will boot to CWM (v5, rev 1.3.4), I've tried loading several different ROMs just to flash something on there to get my device back to square one.
I got in this predicament because I had regular OTA 3.2 and couldn't root. I downgraded to 3.1 (buggy and endless FC), but I was able to run gingerbreak for rooting, do a backup (titanium) and my impression at that point was I could flash a custom mod through CWM.
Nothing is working. I have formatted the sd card in CWM and tried ROMs like Thor 14.2, Tabooney 3.0 and several 3.1/3.2 Acer stock ROMs. After wiping data/factory, wipe cache, wipe Dalvik and Battery Stats and then trying to load a zip file from /sdcard it either tells me the installation fails (which most believe is a bad dl), or (in the case of CWM_ROM_A500_701414_GEN1.zip), the install actually goes through - Finding update...opening update...Installing update... - but whenever I reboot after a *successful* install my device just hangs at the Acer logo/splash screen forever.
I've tried resetting the device (power/ + vol /lock on/off/on/off) and it hangs for a long time Erasing Cache.
I'm overwhelmed. I just want to get a stock ROM on that will install successfully so I can have a functional machine back. Can someone tell me if I'm doing something wrong or what I can do here? Thanks
Never mind
I used a different SD card and that did the trick
jcs1 said:
I used a different SD card and that did the trick
Click to expand...
Click to collapse
Enjoy the little things in life
Probably have a corrupted SD. Might just do a full format on it and still be usable.
Now, I dont usually open threads, but I have an issue here. I've searched and read a lot on how to recover the U8800 in case its soft-bricked, but I've tried the reflashing 2.2 method (Fails in about 5 seconds), Linux method (blefish's method, buzzcomp's method could not yield any results. I connected the phone in the bootloader mode (pink screen) to a Linux PC, but it doesnt appear as a new device there.
Then I tried to upgrade to 2.3, it installs fine, automatically enters recovery (formats data, cache etc), reboots a lot of times (bootloop?). So now whenever I on my phone, the Huawei logo just keeps flashing.
I've also tried to replace the files when connected in the pink screen by replacing the boot.img , recovery.img, amss.bin , EMMCBOOT.mbn file, yet it bootloops.
Prior to this, I had downgraded from Aurora to the stock 2.2, which worked fine. Then I replaced the stock recovery with CWM (the correct one, not the U8800 Pro's). I did the usual clearing of cache, data, formatted system, wiped dalvik cache in order for me to upgrade to a new ROM. Everything went downhill from there
UPDATE : I managed to get 2.3 to be installed. But everytime I enable "USB Debugging", upon the next reboot, there will be a lot of apps which closes unexpectedly, like the Huawei Launcher, Google Framework etc etc. I've tried B526 and B528, but everytime I have "USB Debugging" enabled, this happens. It works fine on 2.2 though
UPDATE 2 : After my fresh installation of the official 2.3, I'd changed the launcher to Holo Launcher, but it fails at starting up. If it does, it keep saying that Holo launcher has closed unexpectedly. The only way to fix it is to boot into recovery and wipe data.
Any help?
bump
U make mistake when you using more method to repair that device. Do you repartition before this. U must back to official partitiob fisrt. Flash that official partition once only not like the tutorial. I face that problem before but everything good now
Sent from my u8800 using xda premium
yusopa said:
U make mistake when you using more method to repair that device. Do you repartition before this. U must back to official partitiob fisrt. Flash that official partition once only not like the tutorial. I face that problem before but everything good now
Sent from my u8800 using xda premium
Click to expand...
Click to collapse
Where can i find the stock partition flash file?
I've found the original partition file from geno, flashed it then installed the official 2.3
everything seems fine, but if i change any settings like turning off fast boot, USB debugging, etc, the phone will bootloop.
UPDATE : I had fast boot disabled, booted in, and now I'm flooded by FC notifications....
I've found the original partition file from geno, flashed it then installed the official 2.3
everything seems fine, but if i change any settings like turning off fast boot, USB debugging, etc, the phone will bootloop.
UPDATE : I had fast boot disabled, booted in, and now I'm flooded by FC notifications....
Click to expand...
Click to collapse
hey i have this same mistake, i have the first boot fine after installing the official rom, but when i reboot the phone in normal boot (diisable fastboot) the phone gets bootloop, so i can't root it in order to put a new rom. i've downgrade to 2.2 froyo and get sum errors after installation but seems to work fine with 2.2 (can even root and install cwm).
after this i try again to upgrade to 2.3 official gingerbread, fist boot is fine, but when i reboot i get again stuck in bootloop... pls help
I am having the exact same issue, does anyone know how to fix this?
The problem is solved？
zgulia22 said:
The problem is solved？
Click to expand...
Click to collapse
I dont know for sure. I flashed another B528, same issues. Tons of FC messages.
I flashed an older B517, installed CWM, flashed DZO's excellent Aurora 5.0, and everything seems fine, for now.
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
jpeclf said:
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your help but seeing as your phone is an Android phone, I don't think the same process applies. But thanks for the effort, I have this baby up and running now.. I just had to reflash the ROM.. Thanks again :good:
FocusHelp said:
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
Click to expand...
Click to collapse
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Be VERY sure you flash the correct ROM for your phone. If you have a version 1.3, then ONLY flash 1.3 ROMs to it. If you have a version 1.4, then ONLY flash 1.4 ROMs to it. You can find the version number under the battery on the sticker. If you flash the wrong version of ROM to it, you will end up with a brick.
When having problems like this, I would recommend flashing the Stock ROM to it first to set everything back to normal. Then, if that works fine, go to custom ROMs if desired. Stock flashing will replace everything back to new settings, including spl, radio, etc... Some of the custom ROMs are truly worth flashing, FASTER, stable, nice features.
Unokashi01 said:
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Click to expand...
Click to collapse
I know I had 3.05a and reflashed 3.10a Clean Rom.. It works great now... I remember I use to have problems with the 3g but not after reflashing it works great
Hello all,
I realize you all are busy but I'm at my wits end here. I installed my bootloader and recovery using afterOTA. This worked really well, I installed Thor 1.7.3 recovery and ICS V8 bootloader using the utility. I then booted into recovery and did a factory reset (really), reset cache and dalvik, battery settings as well... I then went to install ZIP (JB 4.1.2 CM10-FLEX v6supercharged_Aroma-Rev3.4) from internal storage (download folder). I customized the ROM then went back and installed the random apps...
After this was done I hit next and installed the ROM. It didn't take as long as I thought it would, and I hit reboot when it was done, but came to a screen that I could press next on. The installer screen said it was installing permissions, it didn't say that it was completely finished, just installing permissions or something, but I was able to press next.
After rebooting, it started the stock android boot animation, got to the upgrading applications screen, after the applications were done "optimizing" it went back into the stock android boot animation. It never came out of it.
I'm confused as to what I am doing wrong.. I've flashed ROMs multiple times and I thought this one would be the easiest out of all of them considering I didn't care about the data on it and I'm just playing around.
Any help would be appreciated. Thanks!
Fixed.. I'm an idiot
GermanDoerksen said:
Hello all,
I realize you all are busy but I'm at my wits end here. I installed my bootloader and recovery using afterOTA. This worked really well, I installed Thor 1.7.3 recovery and ICS V8 bootloader using the utility. I then booted into recovery and did a factory reset (really), reset cache and dalvik, battery settings as well... I then went to install ZIP (JB 4.1.2 CM10-FLEX v6supercharged_Aroma-Rev3.4) from internal storage (download folder). I customized the ROM then went back and installed the random apps...
After this was done I hit next and installed the ROM. It didn't take as long as I thought it would, and I hit reboot when it was done, but came to a screen that I could press next on. The installer screen said it was installing permissions, it didn't say that it was completely finished, just installing permissions or something, but I was able to press next.
After rebooting, it started the stock android boot animation, got to the upgrading applications screen, after the applications were done "optimizing" it went back into the stock android boot animation. It never came out of it.
I'm confused as to what I am doing wrong.. I've flashed ROMs multiple times and I thought this one would be the easiest out of all of them considering I didn't care about the data on it and I'm just playing around.
Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Well, I kept working on it and I think I was just impatient. Maybe. Either way I went back and tried to reflash several times, doing the wipes from the wipe screen each time. No luck. Eventually I went and formatted the /system /data and all the other options in the mount/storage menu. I then did all the "wipes" again and reflashed. It worked this time! Running incredibly smoothly.
Thanks for reading everyone.