Well, I'm not sure why this is happening, since I didn't see any other comments about this in the development thread, but when I flashed Alien, the touchscreen stops responding when it boots up. The problem went away when I re-flashed back to the old Gingerbread Beta 4.
Relevant information:
-On AT&T Atrix
-Using Tenfar's new CWM
-Flashed KP's Gingerbread Beta 4
-Flashed [Fruitcake] updated radio
-Flashed KP's Alien and theme
-Upon reboot, screen didn't work
-Flashed back to Gingerbread Beta 4, screen worked again.
Is there anything incredibly basic that I'm missing?
Related
I flashed a couple of different ROMs on my fascinate and got them set up and running beautifully. The problem is when I reboot I get FC like crazy. What am I doing wrong. Sorry if this is a stupid one, I came from OG Droid where everything is much more simple. Thanks..
which roms? 2.2 or 2.1? if 2.2, how did you get it? did you get the official update, or did you flash the odin package, or do it separately?
Evil Fascination 3.4.0 with wipe. Stock kernel. used the cwr found in this threadhttp://forum.xda-developers.com/showthread.php?t=1048380
I just flashed gingerREMIX beta 6 and everything ran fine for a while. Before I flashed the new rom I did a full wipe. I have the new radio (MR2) and im running Imoseyon GB lean kernel.
The problem that I have now is with my lockscreen. The phone works i just can not unlock it. its like the lock screen is off the actual screen. Is there another way I can boot into Recovery?
ADB isn't recognizing the device so that's out.
I'm not feeling too good about this
EDIT: With more messing around I figured I was holding the wrong button and now able to get into recovery
Ok, so I flashed JT's Vanilla gingerbread rom using CWR 4 and everything seemed fine. I then flashed B Boy Blizzard theme and everthing ran fine for about twenty mintes, then I got what I thought was the sleep of death (only when I pressed the sleep button). I pulled the battery and powered the phone back on. The phone booted into recovery and I got and error 7 cache recovery unable to mount message. I really like what little of the rom I saw and the theme. I sure at this point I'll have to Odin back to stock as I can't do a recovery either (same error message). What I'd like to know is this just a problem I'm having or is there something wrong with the rom or theme? Please advise. Thx in advance.
I have had alot of problems with that rom aswell...not really sure whats going on. Sometimes the rom will install with cwm 4 other times it just boot loops. I have tried every install method for that rom and nothing yet seems reliable. I have no problems flashing other roms, so idk... just chillin with powerwash right now until the bugs get worked out w/ VGB(hopefully).
All of his themes (at this moment) are based on 080211 v2 VGB. And between v2 and v3 there were framework and other apk changes i.e. settings. So flashing that theme on top of v3 will surely lead to issues. Just reflash rom. And make sure the theme you try only says for v3.
good day.
Also, you wont boot into the right recovery using the 3 finger method. you need to use adb or the reboot options
Ive just installed Clockwork Mod v4 and Cyanogenmod (latest) and i am stuck on a screen loop with repeatively shows the Cyanogen loop with the blue droid on the skateboard with a circle around him- it keeps repeating the full cycle over and over again, i have taken the battery out but nothing, help?
Try re-flashing the rom, see if it changes
Yeah i managed to fix it thanks to another guy on these forums- reflashing Clockwork did the trick.
Had exactly the same problem with my G5, Flashed one. Fine. Flashed the 2nd one and it boot looped, flashed a different firmware and the same thing happened, weird! Closed/repoened odin Disabled auto reboot and flashed CM7 and it was fine
i experienced this too when I first tried flashing cm7.1, plus the I5503DXJP7 baseband, after using the MAD rom for a good 4 months or so. I reflashed the stock 5503 rom, then upgraded the baseband and again experienced the boot loop.
i found a 5503 rom on samfirmware that came with the I5503DXJP7 baseband i needed. that one booted up fine. then i flashed cm7.1. that worked fine too. so this turned out to be a problem with the baseband (i think).
but cm7.1 came with this crazy loud headset volume and i use the g5 a lot for calling at work. had to go back to MAD2.0.9, this time flashed using CWM (very cool: thanks to whoever got that onto the G5)
I fixed this problem a while back aha, thanks for the replies though
Currently awaiting for my phone to be repaired -.-
I had the same problem...I repeated the steps and obivliously it worked
I used the CM7 for a while. I reflashed the stock ROM and the bootloop started. Than i freaked out and reflashed all by odin. It works.
Sent from my GT-I5500 using Tapatalk
I apologize to everyone if this has been answered (I'd be surprised if it hasn't but couldn't find it using search).
I recently moved from a v1.1 bootloader ROM to a v1.2 bootloader ROM. While I was on the v1.1 bootloader I enjoyed using ClockworkMod .8 to do my flashing/installing/clearing/wiping/backing up and restoring. Now that I've have to rely on the Stock recovery to install my current v1.2 ROM I really miss having the ease of use of ClockworkMod. I am currently using Roebeet's Mountain Laurel 3.1.0 ROM but it's got the stock kernel and aside it from feeling sluggish (compared to VEGAn 5.1.1) I can't get VPN to work on it.
Using his instructions I "enabled" Clockwork that is supposed to be compatible with v1.2 ROMs on this tablet and actually succeeded in booting into Clockwork recovery. After Clockwork came up I flashed Pershoot's last Froyo kernel for the gTab and then rebooted. It came up stuck on the birds screen and I had to NVFlash back to where I started from.
So my question is has anyone successfully installed Clockworkmod v3.0.2.8 on the gTab running a v1.2 ROM and was able to flash a custom kernel and the tablet didn't get stuck on boot or suffer any other reboot related problems? My current experience is that only the Stock recovery is happy on my tablet with this ROM for some reason.
Any info that would get me to the point where I can run this ROM with Pershoot's last gTab FroYo kernel (7/27/11) successfully would be greatly appreciated.
Regards,
Steve
Update: I really owe everyone an apology for having overlooked such an obvious piece of information that would have made the hassle of the last few days of near-constant NVFlashing unnecessary. The instructions from Roebeet was fine, the problem was me (of course; user-error). ClockworkMod was working fine and is now still working fine on my gTab. The part that was the obvious thing that I should have noticed earlier was that the version of Pershoot's last FroYo kernal for the gTab had 2 versions (1 for the 1.1 bootloader and another for the 1.2 bootloader). Once I finally noticed that little discrepancy between the kernel zip file I had and the one he listed on his Droid Basement blog site it was smooth going. I was even able to install SetCPU to change my tablet's operating speed and as another bonus I was able to install the 5 VPN app from the Market to expose the VPN settings on the gTab using the Mountain Laurel 3.1.0 ROM and actually set it up to use my VPN account from my VPN vendor (StrongVPN). I am currently in Texas watching a program using the BBC iPlayer app as if I was in the U.K..
Now if I can get the VTL Launcher running on this ROM without it getting into a seizure of force closes I'd be out of things to want for on this ROM.
Anyway, let this be a lesson to everyone here that you don't have to be a noob to suffer a brain-fart.