well i just tried flashing froyo on my nexus one and it worked. but for some reason, flash sites did not work. i tried hulu, it didnt wor. i tried cbs.com, nada. flash is just not working and thats the only reason why i was soooo eager for froyo. i was on the desire rom first but i wiped and downloaded the file from MoDaCo and flashed it but nothing. i guess i will be going back to CM 5.0.6 for now. any body got any answers for my issues? i understand it just came out and people need time to understand it but any help, if there is any, would be really appreciated
PS, i really dont want to go back to stock....or do i have to? my N1 is rooted but idk what the problem is
Install Flash from the market.
i did. its the first thing i installed. i tried uninstalling it and reinstalling it and nothing
okay i got it. i installed CM 5.0.6 and then flashed froyo and it worked. its great
Related
Hello everyone. I'm not sure if this has been posted, I did a search, and didn't see anything related to my issue. I installed the newest 2.1 leak, and my phone will randomly just power itself off. I've wiped the memory and reinstalled a few times. I'm just running the basic system, with Handcent, Pdanet, Droid Live lite, and Astro file manager installed on it. Any suggestions as to what may be causing the problem, or what I can do to try to fix it?
Leak is a curse word around these parts. you said you "wiped" a few times. are you on ROOT? if so, you shouldnt be using the plain root. you should download a ROM, (Ivans 0.8T2, Senseable, Evil Eris...) put it on your sdcard, wipe, then flash one of those. So IF you have ROOT, then change your thread title, otherwise people such as myself may get medieval on you.
Out of curiousity, why shouldn't one use plain root? I have yet to flash a ROM because none of the ROMs seem to be bug free. Am I wrong?
meanm50 said:
Out of curiousity, why shouldn't one use plain root? I have yet to flash a ROM because none of the ROMs seem to be bug free. Am I wrong?
Click to expand...
Click to collapse
the plain root is more buggy than any ROM actually. Ivan's rom has fixed some bugs (not sure which, sorry. but hes trustworthy) and Senseable is just a themed version of Ivans rom. you're better off with a ROM since devs are always working to fix bugs. some but (like the signal standy issue) probably wont be fixed unless HTC releases a newer update for the official release.
Everything is working flawlessly for me, I have had zero issues with this ROM since day one. Maybe I just don't use the phone enough or really stress it, but I have yet to come across any quirks on this leaked 4.5.573. Everything works - gps, netflix, any apps I download, corporate sync, etc. etc.
Is there any sense in upgrading to the latest official OTA GB? I figure if it ain't broke don't fix it...right? Or are there compelling reasons to go ahead with the official OTA? And if the answer is YES UPGRADE, what's the best way to do this considering I'm on 4.5.573 right now? BTW, I'm on Cricket.
I've got this same question. I want to upgrade for several reasons, but what I've read on several sites is that we have to do the SBF thing back to 2.2, then upgrade.
Almost none of the threads I've read at several sites even mention .573 anymore, so I'm not exactly sure of the route to go.
Why do you want to upgrade? Are you running into problems? Unless there's a good reason to upgrade I'd prefer not to, especially if I have to SBF in order to upgrade. That means I'll have to re-do my Cricket flash which I've probably done 50 times now but I'd prefer not to have to do it again.
hey guys,
i am on version 596 of gb, the official version. and i would highly recommend upgrading, there is a new kernel and new baseband. that means the phone runs more smooth and you have cleaner calling and stuff. i have noticed a big improvement in the new kernel and stuff. it would be very beneficial to upgrade in my opinion.
^^^
Those were the reasons I wanted to upgrade. Performance took a GOOD bump in the updates after .573
I just followed the instructions here...
http://www.mydroidworld.com/forums/...new-full-sbf-droid-x-2-3-340-a.html#post56464
Method 2 worked for me, the first one wouldn't detect my phone. I got a boot loop after it finished so I booted into recovery and cleared the cache/data factory reset.
Now it's all fine.
Now to find the right set of GB update roms.
you'll want the updated radio found in the later versions and .596 runs buttery smooth. about a week of heavy use not one reboot or crash.
I gotta say, I'm VERY glad I did it. It was smooth and quick before, but good lord, this is CLEAN.
Not one reboot, not one crash, all NOICE!
i'm on 4.5.573 with root and the phone has been running crazy slow for the last week. will this work? i'm trying method 2 but it will not recognize my phone.
thanks!
RED ZMAN said:
^^^
Those were the reasons I wanted to upgrade. Performance took a GOOD bump in the updates after .573
I just followed the instructions here...
Method 2 worked for me, the first one wouldn't detect my phone. I got a boot loop after it finished so I booted into recovery and cleared the cache/data factory reset.
Now it's all fine.
Now to find the right set of GB update roms.
Click to expand...
Click to collapse
I would reccomend updating to a newer version from team black hat. Its faster, smoother, the blur is different (better) and best of all, pre rooted.
Sent from my Xoom using XDA Premium App
I currrently have a Galaxy s5 sm-g900v. Two days ago, I flashed Alliance rom via Safestrap and everything was great until my wifi starting acting dumb. It refuses to turn on, just hangs. I have tried flashing the modem, and Blaze kernel, hoping it would fix it, but no luck. I unrooted and Odin'd back to complete stock, and it STILL won't work. Somebody please give me some pointers on how I can fix it Help would be GREATLY appreciated.
co.purp said:
I currrently have a Galaxy s5 sm-g900v. Two days ago, I flashed Alliance rom via Safestrap and everything was great until my wifi starting acting dumb. It refuses to turn on, just hangs. I have tried flashing the modem, and Blaze kernel, hoping it would fix it, but no luck. I unrooted and Odin'd back to complete stock, and it STILL won't work. Somebody please give me some pointers on how I can fix it Help would be GREATLY appreciated.
Click to expand...
Click to collapse
i would do a clean wipe and flash stock rooted rom.
i had something similar but not as extreme as yours.
i was on ricks rom and it didnt autoconnect and id have to put in the password everytime i connected.
i clean wiped and installed stock rooted 4.4.4 and all is fine.
keep trying different roms if until you find one that works.
FingerBlastJ said:
i would do a clean wipe and flash stock rooted rom.
i had something similar but not as extreme as yours.
i was on ricks rom and it didnt autoconnect and id have to put in the password everytime i connected.
i clean wiped and installed stock rooted 4.4.4 and all is fine.
keep trying different roms if until you find one that works.
Click to expand...
Click to collapse
Youve posted this in two threads and althought it might work it has nothing to do with ricks rom as many others including myself have been using ricks rom flawlessly.. Id say wipe and flash the rom over again fresh and see if that works.. But saying try another rom isnt a good solution when ricks rom works just fine 99% of the time
elliwigy said:
Youve posted this in two threads and althought it might work it has nothing to do with ricks rom as many others including myself have been using ricks rom flawlessly.. Id say wipe and flash the rom over again fresh and see if that works.. But saying try another rom isnt a good solution when ricks rom works just fine 99% of the time
Click to expand...
Click to collapse
Just giving help to those that need it based on my experiences. It just so happens that ive been on ricks rom and i had that issue. Nothing against rick and his rom but thats the situation and thats how i fixed my issues.
I believe when you are using safestrap you are supposed to flash the kernel modules to get Wi-Fi to work. Or am I mistaken about that?
Thanks guys, but I got it working by factory resetting from stock recovery.
Hello!
Ever since trying out the first OO3 Beta (3.0.0) I have gotten a weird bug, flashing the ROM works fine and everything works all the way until I reboot my phone. It loads through the bootanimation and then it just has a black screen and you can see the notification bar flash every 5 seconds or so. This issue also come up on the newest 3.0.1 beta.
I've tried different ways of flashing using the modified recovery and the modified supersu (also without the supersu) but I still get the same issue. I've tried different OO3 ROMs as well like Skydragon and CyanOxy but I get the same bug.
I haven't seen anyone post something about the same issue so I figured I'd ask, sorry if this already has been answered and I missed it.
Thanks in advance.
Same happend to me, always get that black screen, try to reboot once you are in it, works for me.
I've tried rebooting a few times and still got the same result, unfortunately.
Thanks for the advice anyways!
Hi,
I'm facing exactly same issue since new OTA update...
Did you manage to fix it?
Hey Endoloris.
I haven't been able to fix it yet unfortunately. I've really tried almost everything at this point which makes me think there's something odd with the hardware, but I don't really know.
I'll update this thread if I fix it.
Have you uninstalled the Google Search app?? Every time I trie to uninstall the Google app I get the same problem. Now I just let it on my phone.
Edit:
Have you flashed the right firmware for OxygenOS 3??
LordHelmchen89 said:
Have you uninstalled the Google Search app?? Every time I trie to uninstall the Google app I get the same problem. Now I just let it on my phone.
Edit:
Have you flashed the right firmware for OxygenOS 3??
Click to expand...
Click to collapse
Yes, I've tried both those options. I've tried pretty much everything. I even tried restoring the phone to stock 2.2.1 and then updating via OTA and I still got the same issue.
So the weird thing is that I get the same issue on the new Paranoid Android ROM released today.
Adhas said:
So the weird thing is that I get the same issue on the new Paranoid Android ROM released today.
Click to expand...
Click to collapse
Really strange...sorry,but Ican't help you then. Maybe you ask one of the devs with pm.
---------- Post added at 04:07 PM ---------- Previous post was at 04:02 PM ----------
Are you realy sure, that you flashed the right TWRP and firmware?? Or do you use a custom kernel.
Sorry, my last ideas...
I did try different firmwares, it didn't work at all with the old ones for obvious reasons. I tried the twrp 3.0.2 Hybrid, a custom recovery when the first Oxygen 3 beta came out (was orange), and I tried the recovery made by Grarak recently. I also tried using stock recovery and flashing.
No custom kernel, I've tried flashing with the modified Supersu but I was thinking that it might be causing the issue so I tried without root and I still got the same result.
In the same boat here, was running official CM, then this happened.
hey guys long time lurker, recently my s7 edge crashed, after using default rom, i decided i wanted a custom rom anyway and picked one, installed it correctly everything was working fine for about 2 weeks. crashed, started constant boot loops, so i reinstalled the rom as before, and still constant boot loops.
then i found official roms and put them on instead, anything 7+ didnt work, but when i put on 6.xx it would work, but using samsungs inbuilt to upgrade it would begin to bootloop again.
any help appreciated!
SM-G935FD
australia
Did you try flashing 7.0 rom with the same baseband version of your phone?
Tried many of the available roms. Found one that is working and I will stick with it for now. Still would like to figure out what I did wrong though, and why I can't flash stock 7.xx
stuartroad said:
Tried many of the available roms. Found one that is working and I will stick with it for now. Still would like to figure out what I did wrong though, and why I can't flash stock 7.xx
Click to expand...
Click to collapse
Did you clear cache, data?
ManXXXX said:
Did you clear cache, data?
Click to expand...
Click to collapse
Yep