Hi there!
After almost 2 days from my holydays trying to install cianogen beta3 in my defy I lost almost all my hopes. Than I made my last call, I tried a version older, and GOTCHA! I have cyanogen working.
So the problem is, if i try installing beta3, all that I get is a black ugly screen after moto logo.
And with a test version before beta3 cyanogem works like a charm.
I already tried with the nordic, korean and uk roms, and tried too patching pays rom 3 and 5.
Also i got some weird error with SuperOneClick2.1 than i used SuperOneClick 1.65
Also, again, i tried to update beta3 from the test with and without wipe, and no luck.
Any sugestions to me to get the beta3 working?
I'm guessing you have, because you got an earlier release working, but are you doing the 2nd INIT boot with the boot menu thingo? cuz thats why i copped a black screen when trying to get it to work
I suppose he already has 2ndinit working considering he has it working before though?
Thanks for the answers. Yeah i needed the second init thing to make the test build work. The only strange thing that i see is a error message that sometimes i got whenever i install beta 3 saying that xbin/su dont exist. when i got this message i try install it again and says that it was completed. But when i install the test build i never get this message.
Related
Hi there
I think I destroyed my CPU or something ... I used a custom kernel which does OC and UV and it worked without any glitches for about 8 hours.
Then it froze and now I cannot boot any rom.
If there is user data it boots to a frozen lockscreen.
If I do a factory reset it says that the Process system is not responding...
Anybody got an idea?
I just flashed the official SLCD RUU and now it works again ...
I can only run official ROMs
If I root and flash a new one, the same error persists!
anybody any idea?
I cannot really tell HTC to replace my phone, it works with their froyo version :S
but I don't like Sense and now I'm stuck using it ... hate that -.-
Well you rooted with an RC of unrevoked. Could as well have something to do with that. Have you tried custom sense roms? Just to see if they work. Else, i would try the downgrade-to-hboot-0.83-method.. just practice the screenless method with the screen turned on, i managed to do iy in one attempt (H)
I'm having a little trouble with the new Sith 2 Rom. I was wondering if, hopefully an expert, is willing to chat with me and give me some support.
Details:
--Rom is Flashed but when I do any type of shutdown/reboot. It freezes
--When I try to load up TWRP Recov.. It freezes on the logo
--When I do get in the menu if lucky, any action I do freezes
Note:
I did have ClockWork when I first flashed Sith 2, but I still had the same issues. So I installed TWRP to re-flash but I never got the chance to try.
---------------------------------------
Update:
--Flashed TWRP 2.2 and fixed all problems.
Just thought I'd mention it since there's always a possibility that I may not be the only one with the issue.
Hi there!
I installed
http://forum.xda-developers.com/showthread.php?t=1912187
with basbeand 77 instead of the recommended ones, and it appeared to work just fine for two days.
Today, I installed the LBE Guard, and so my Desire was stuck in bootloop, which I could get out of after a fullwipe and a new install.
So, then, I installed the LBE privace Master (v4.3.2738),
http://forum.xda-developers.com/showthread.php?t=1422479
because I read it was okay for JB. While configuring it, my phone crashed, and I was again stuck in a bootloop. I tried to make a fullwipe again, and a new install, but I have still these random (but appearing soon after booting) crashings and then a bootloop. It even appears when I use the Aroma Installer, but not in the CWM.
So my question is - what went wrong and more importantly, how do I get my phone to work again?
Thanks for replying.
The part with the baseband is wrong - that was my other phone.
I am quite the noob-cookie, I also have the problem with random reboots and freezes. I have been messing around with the new Nikez 4.2 Jellybean Rom, i thought that could be the reason why. But now I am also experiencing it with the old Nikez 4.1 Rom that used to be very stable for me. Anyone know a good solution? I have done several full wipes..
Cheers!
D851 here, When ever i switched from cloudy 2.5 to blisspop 4.0 and after wiping everything i flashed a various of radios bootstacks and etc to make it boot after many failed attempts to boot ( it boots up but after 4 or so seconds after the lg logo the screen turns black and doesnt turn back on until after i pull out the battery) it worked after i flashed the rom WITHOUT a custom kernel so naturally i booted up just fine and thought maybe now i set up everything on my phone and tweaks i should go back and flash a custom kernel i used to use (777 r16) but then it gave me the problem i faced before the black screen after the lg logo no kernal would work. THEN another problem arised similar to the freezing on the black screen randomly during a usage thru my day the phones screen would be unresponsive animations but touch wouldnt work and i know its not my screen cause when i flash back to cloudy it works fine the freezing happens at least every 5 mins. someone halp?
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
warrior420 said:
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
Click to expand...
Click to collapse
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
thelgog said:
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
Click to expand...
Click to collapse
Okay.
Well, when I was flashing I never flashed a kernel.
Ill be getting a brand new Anker Battery in the mail today. Ill report my findings.
I ended up going to a stock based rom and the issue never happened. So I stuck with it. Ill have to do some testing later and ill let you know how the battery works.
It's not the battery
I downgraded my T-Mo G3 since I couldn't root it with LP on it. Went back to 4.4.2., rooted it, TWRP'd it, and installed the latest CM12 Nightly, Gapps, SU, etc.
As long as the sim card was OUT the installation was great on wifi only, As soon as I put it in it shut off right after, or during boot up. Take the sim out and it works. And yes, the only way to get back into recovery was pulling the battery and doing the key press to recovery. Mystified.
If I find out anything, I'll post it here.
I'd say do a complete return to stock, upgrade via LG Mobile Support tool all the way to 20G, see how it works stock for a while. Then root ( http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 using the first method) and see what happens.
Hi. I had been using my galaxy note 2 just fine untill recently when I tried to flash gapps. It was incompatible. Anyway, I freaked out because everytime i tried to get y phone it was st showing a black screen saying setup wizard is incompatible. I formatted my phones data. Now, I still can get into TWRP, and still can put ROMS on my phone, buut everytime I flash the i get the same seutp wizard error.
By the way, I was sing the Cyanide OS with shift Kernel, and thats where the setup wizard doesn't work. I've also tried Ressurection Reimx, but got a bootloop
Is the phone's model # sgh-i317 from AT&T? You have confirmed that the Gapps being flashed are for the version of Andoid on the phone? Tried different versions of Gapps?
oinkao said:
Hi. I had been using my galaxy note 2 just fine untill recently when I tried to flash gapps. It was incompatible. Anyway, I freaked out because everytime i tried to get y phone it was st showing a black screen saying setup wizard is incompatible. I formatted my phones data. Now, I still can get into TWRP, and still can put ROMS on my phone, buut everytime I flash the i get the same seutp wizard error.
By the way, I was sing the Cyanide OS with shift Kernel, and thats where the setup wizard doesn't work. I've also tried Ressurection Reimx, but got a bootloop
Click to expand...
Click to collapse
What TWRP are you on. When u used cyanide mm something hastened
Happened to where I had to Odin to stock and start all over