I am pretty sure that I have a borked radio. I was running a "pre-flicker fix" Avatar ROM and upgraded to the 10-22 CM nightly. It worked great for about 4 hours and then lost the ability to send texts or make calls. I am trying to work my way through the steps to fix a messed up radio. I downgraded TWRP to 2.3.3 so I could apply the stock ROM, but the stock ROM hangs on the boot screen. I did apply the correct boot.img.
What am I missing?
evolwun said:
I am pretty sure that I have a borked radio. I was running a "pre-flicker fix" Avatar ROM and upgraded to the 10-22 CM nightly. It worked great for about 4 hours and then lost the ability to send texts or make calls. I am trying to work my way through the steps to fix a messed up radio. I downgraded TWRP to 2.3.3 so I could apply the stock ROM, but the stock ROM hangs on the boot screen. I did apply the correct boot.img.
What am I missing?
Click to expand...
Click to collapse
Did you happen to do a full clean wipe before flashing the 10/22 nightly?
evolwun said:
I am pretty sure that I have a borked radio. I was running a "pre-flicker fix" Avatar ROM and upgraded to the 10-22 CM nightly. It worked great for about 4 hours and then lost the ability to send texts or make calls. I am trying to work my way through the steps to fix a messed up radio. I downgraded TWRP to 2.3.3 so I could apply the stock ROM, but the stock ROM hangs on the boot screen. I did apply the correct boot.img.
What am I missing?
Click to expand...
Click to collapse
I would retry flashing the stock boot.img using fastboot. Sounds like it didn't take.
mdmower said:
I would retry flashing the stock boot.img using fastboot. Sounds like it didn't take.
Click to expand...
Click to collapse
I have tried flashing the boot.img a couple times, I thought the same thing.
I tried it one more time right be for I clicked "submit reply" with no luck.
TheGOAT232412 said:
Did you happen to do a full clean wipe before flashing the 10/22 nightly?
Click to expand...
Click to collapse
I did not do a full factory reset, but did wipe dalvik, cache, system and data.
evolwun said:
I did not do a full factory reset, but did wipe dalvik, cache, system and data.
Click to expand...
Click to collapse
You installed the rom AFTER wiping /system... right?
mdmower said:
You installed the rom AFTER wiping /system... right?
Click to expand...
Click to collapse
Yes
Ok, so I am getting close to having a fully functional phone. I got it working, but it was all luck. (note: I tried each of these steps before, just not in this exact order)
a. I installed a TWRP backup of my Avatar ROM
b. flashed the appropriate boot.img
c. then flashed the Avatar ROM and gapps over the top of the backup.
It is functioning, but I am unable to access the internal storage. In ES Explorer, I can get to "/external_sd/"(which contains files) and "/mnt/sdcard"(which is empty) but if I try to click on the sd card icon it says "SD Card empty, unmounted or not present. I am unable to save screenshots and pictures because of this. This could stem from the SD swap I did.
Now that I have the radio working, I think I want to just start over with the device, without the sd storage, some of the apps are not working correctly. The factory reset I did blasted a lot of stuff. Also my download speeds are VERY slow... it says 4G but I don't believe it. Does anyone have a link to a good walk through on completely starting from scratch on a phone? What is the most stable CM ROM that does not have screen flicker?
thanks for the help guys
I had this exact same issue with 10/22. The radio died, and in the process of trying to fix it, the internal sd disappeared.
I ended up doing a full RUU following the steps at unlimited.io (ignoring the chmod step and the sudo parts of the commands since I'm in Windows). Then, HTCDev unlocking again, installing TWRP and Viper. Now, it seems to be working okay.
I'm having bad luck flashing the CM nightlies lately, not sure if it's just my phone, but I had the same issue even with the 10/18 experimental build.
I did end up getting it going. I built off of what I did in my previous post. I have to format the phone's data partition (mounded via TWRP) to get it to go.
Related
Hopefully I can get some help from you guys I'm currently on hboot 1.12 HTC devunlock and I'm running TWRP 2.2.1. I tried flashing CMX but I get "unfortunately phone isn't responding" right after that it says the UI isn't responding and the dialog boxes keep appearing. So I can't get past the lock screen. I've already tried wiping and reflashing and it didn't help. Any help would be appreciated.
gespinal0301 said:
Hopefully I can get some help from you guys I'm currently on hboot 1.12 HTC devunlock and I'm running TWRP 2.2.1. I tried flashing CMX but I get "unfortunately phone isn't responding" right after that it says the UI isn't responding and the dialog boxes keep appearing. So I can't get past the lock screen. I've already tried wiping and reflashing and it didn't help. Any help would be appreciated.
Click to expand...
Click to collapse
IF S-ON = True:
Then you have to flash the boot.img kernel file via fastboot. I would also try downloading the ROM file again and double checking MD5 just in case.
IF S-OFF = True:
Download the ROM again and check the MD5, make sure you wipe the hell out of your phone, and if your coming from another ROM or Stock, don't recovery any Nandroid info, you should have to reinstall your apps or recover via MyBackup or Titanium Backup (app + data, no system apps).
megabiteg said:
IF S-ON = True:
Then you have to flash the boot.img kernel file via fastboot. I would also try downloading the ROM file again and double checking MD5 just in case.
IF S-OFF = True:
Download the ROM again and check the MD5, make sure you wipe the hell out of your phone, and if your coming from another ROM or Stock, don't recovery any Nandroid info, you should have to reinstall your apps or recover via MyBackup or Titanium Backup (app + data, no system apps).
Click to expand...
Click to collapse
I thought it was only if you had updated to 1.15 for the hboot that you have to flash the bootimg..... nvm ill try it once i get home
Definitely sounds like you might have a bad download. Also download the superwipe zip and use that too. With hboot 1.12 you should be fine to flash without any special procedures.
Sent from my EVO using xda premium
A known issue in CMX is that phone process will crash, it does this while the phone searches for a signal, once a signal is found it should stop. Just try waiting it out, it doesn't really affect anything, once the message is gone you will be fine
durandetto said:
Definitely sounds like you might have a bad download. Also download the superwipe zip and use that too. With hboot 1.12 you should be fine to flash without any special procedures.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
om4 said:
A known issue in CMX is that phone process will crash, it does this while the phone searches for a signal, once a signal is found it should stop. Just try waiting it out, it doesn't really affect anything, once the message is gone you will be fine
Click to expand...
Click to collapse
i tried the bootimg and i still had the same problem, but ill try waiting it out
megabiteg said:
IF S-ON = True:
Then you have to flash the boot.img kernel file via fastboot. I would also try downloading the ROM file again and double checking MD5 just in case.
IF S-OFF = True:
Download the ROM again and check the MD5, make sure you wipe the hell out of your phone, and if your coming from another ROM or Stock, don't recovery any Nandroid info, you should have to reinstall your apps or recover via MyBackup or Titanium Backup (app + data, no system apps).
Click to expand...
Click to collapse
That is only for HBOOT 1.15 and up. HBOOT 1.12 allows for flashing of kernel from recovery with S-ON.
When you say you tried "wiping and reflashing", what exactly did you wipe? You should do a factory reset, then wipe data, system, cache, and dalvik. Then flash the ROM.
bilbo524 said:
That is only for HBOOT 1.15 and up. HBOOT 1.12 allows for flashing of kernel from recovery with S-ON.
When you say you tried "wiping and reflashing", what exactly did you wipe? You should do a factory reset, then wipe data, system, cache, and dalvik. Then flash the ROM.
Click to expand...
Click to collapse
Im running Viper4g on my evo lte 4g its a sense based rom i wipe the system, then dalvik cache, and cache. Ill try the factory reset now.
gespinal0301 said:
Im running Viper4g on my evo lte 4g its a sense based rom i wipe the system, then dalvik cache, and cache. Ill try the factory reset now.
Click to expand...
Click to collapse
Don't forget data too
One user kept corrupting his phone with a backup of user data, I don't know how or where he got the relevant knowledge to obtain just an image apps and user data but it was corrupt and he stuck himself in an endless cycle of reformat and reflash apps and data. A human boot loop lol I was thinking about adding it to the troubleshooting guide but what are the odds that someone who doesn't know what they are doing will create a zip install of backed up data (or fail really since it is corrupt) and flash it *looks around in baited breath* well OK then
Well i think the factory reset worked now i get a not so frequent dialog saying process.phone.android has stopped. Should i reflash or just wait it out? lol
I would wait it out
I had this exact same problem. My issue was I had flashed a modified mail app that got rid of the Exchange Security Lock. Once I factory reset I was fine. When I tried flashing that Mail app again, I got the same Phone has quit error over and over.
gespinal0301 said:
Well i think the factory reset worked now i get a not so frequent dialog saying process.phone.android has stopped. Should i reflash or just wait it out? lol
Click to expand...
Click to collapse
That is a known issue with CM10. Phone process will force close upon boot until you get a signal. Once you get a signal, it will be fine, and not happen again until you reboot.
xuohtx said:
I had this exact same problem. My issue was I had flashed a modified mail app that got rid of the Exchange Security Lock. Once I factory reset I was fine. When I tried flashing that Mail app again, I got the same Phone has quit error over and over.
Click to expand...
Click to collapse
I didn't use titanium backup the Play Store just started installing everything I needed which was why I thought it was weird. Everything is working great so far. Thanks to everyone for their input and help.
Google market back up has been a long time feature. Its just that OEMS won't include it or for some reason disable it. Every HTC Android phone I have own has asked permission for Google market back up but upon factory reset or flash, sense will disable it the automatic restore
bilbo524 said:
That is a known issue with CM10. Phone process will force close upon boot until you get a signal. Once you get a signal, it will be fine, and not happen again until you reboot.
Click to expand...
Click to collapse
I also get the force close of the phone when I toggle airplane mode. Sometimes it doesn't stop and I have to reboot.
Sent from my EVO using Tapatalk 2
bilbo524 said:
That is a known issue with CM10. Phone process will force close upon boot until you get a signal. Once you get a signal, it will be fine, and not happen again until you reboot.
Click to expand...
Click to collapse
echo....echo...echo..nah I kid, just a bit bored haha
Lost data after Beast 4.3 / or to sideloading and dirty-installing the M7 rom. Flashing different roms/radios made no difference.
SOLUTION TO DATA LOSS:
LakerStar25 said:
Just a heads up to anyone that's on the Verizon version having extreme data loss. If you messed with your apn it could have screwed something up were you might need to run the RUU to fix. It happened to me and micromod. So if that has happened and have tried to get data back and nothing has worked you will need to
1. Nandroid then install the pre ota hboot
2. Relock
3. Backup internal memory then Run RUU
4. After RUU finishes do a factory reset.
5. Reboot and data should be back.
6. Unlock if desired or just install ENG hboot and install recovery and flash your nandroid and good to go.
Click to expand...
Click to collapse
Watercycle said:
Was running Newt's M7, and flashed beast 4.1 fine, wanted to try flashing beast 4.3
After flash it began to boot-loop and ( foolishly ) without a backup I had to use ADB sideload to reflash M7. That worked, but now I have no data, it won't detect the sim card. Tried reflashing the radios+hboot ( yes unlocked and S-off ) to no avail.
Backed up to a stock rom made after S-off but that also doesn't have data ( and keeps yelling "droid" every 10 seconds ).
Click to expand...
Click to collapse
at this point I would suggest going back and read the flashing your recovery. Then after you do that go back in and try and flash kernel again.seems like all your problems are caused by bad last of the kernel.
Watercycle said:
Was running Newt's M7, and flashed beast 4.1 fine, wanted to try flashing beast 4.3
After flash it began to boot-loop and ( foolishly ) without a backup I had to use ADB sideload to reflash M7. That worked, but now I have no data, it won't detect the sim card. Tried reflashing the radios+hboot ( yes unlocked and S-off ) to no avail.
Backed up to a stock rom made after S-off but that also doesn't have data ( and keeps yelling "droid" every 10 seconds ).
Click to expand...
Click to collapse
have you tried reseating your sim card?
slimc84 said:
have you tried reseating your sim card?
Click to expand...
Click to collapse
Yes, tried reseating, no luck.
Also just tried cube's 'return to stock' zip along with reflashing beast 4.1, still without phone/data
Watercycle said:
Yes, tried reseating, no luck.
Also just tried cube's 'return to stock' zip along with reflashing beast 4.1, still without phone/data
Click to expand...
Click to collapse
reboot your phone and toggle airplane mode off and on waiting about 20 seconds in between
slimc84 said:
reboot your phone and toggle airplane mode off and on waiting about 20 seconds in between
Click to expand...
Click to collapse
Tried airplane spam for 3 minutes or so, no go.
Currently on stock and just flashed cubed kernel and modules, still no data.
Watercycle said:
Tried airplane spam for 3 minutes or so, no go.
Currently on stock and just flashed cubed kernel and modules, still no data.
Click to expand...
Click to collapse
sounds like it may be a SIM card error...might have to get a new one....
SOLUTION TO DATA LOSS:
LakerStar25 said:
Just a heads up to anyone that's on the Verizon version having extreme data loss. If you messed with your apn it could have screwed something up were you might need to run the RUU to fix. It happened to me and micromod. So if that has happened and have tried to get data back and nothing has worked you will need to
1. Nandroid then install the pre ota hboot
2. Relock
3. Backup internal memory then Run RUU
4. After RUU finishes do a factory reset.
5. Reboot and data should be back.
6. Unlock if desired or just install ENG hboot and install recovery and flash your nandroid and good to go.
Click to expand...
Click to collapse
I have spent the whole day flashing and trying to get my data back. I am so happy that LakerStar took the time to write out those steps. After flashing RUU there was still no data, but factory reset afterwards did the trick!
Watercycle said:
SOLUTION TO DATA LOSS:
I have spent the whole day flashing and trying to get my data back. I am so happy that LakerStar took the time to write out those steps. After flashing RUU there was still no data, but factory reset afterwards did the trick!
Click to expand...
Click to collapse
awesome. Please change your OP title to note fix found please.
Hi,
I have a very strange problem now (at least for me).
First some facts about the phone: It's unlocked Virgin Mobile phone, S-off, rooted, and has a usable 4ext recovery installed.
I also did some days ago when 4ext was installed a backup before trying anything else.
After that I tried different ROMs and most of them booted fine after flashing, and I used the last 2 days a JB 4.3 ROM until I found problems with the camera and wanted to see how this is for one of the other ROMs I tried before.
But after try to flash another ROM, it was stuck with on the HTC logo (the same ROM I flashed before without any problems, and of course after wiping all internal partitions like always). Also flashing any other ROM didn't help - even restoring the backup from the original ROM didn't solved this. Only using fastboot from the computer to write the boot image changed the hanging on th HTC logo in a boot loop now - and still no usable flashing is possible.
Does anyone has any ideas what the reason for this could be and how it can be solved to have a working phone again?
Thanks!
mec75 said:
Hi,
I have a very strange problem now (at least for me).
First some facts about the phone: It's unlocked Virgin Mobile phone, S-off, rooted, and has a usable 4ext recovery installed.
I also did some days ago when 4ext was installed a backup before trying anything else.
After that I tried different ROMs and most of them booted fine after flashing, and I used the last 2 days a JB 4.3 ROM until I found problems with the camera and wanted to see how this is for one of the other ROMs I tried before.
But after try to flash another ROM, it was stuck with on the HTC logo (the same ROM I flashed before without any problems, and of course after wiping all internal partitions like always). Also flashing any other ROM didn't help - even restoring the backup from the original ROM didn't solved this. Only using fastboot from the computer to write the boot image changed the hanging on th HTC logo in a boot loop now - and still no usable flashing is possible.
Does anyone has any ideas what the reason for this could be and how it can be solved to have a working phone again?
Thanks!
Click to expand...
Click to collapse
Maybe your sd card is corrupted. Try another card if you have one around
What hboot?
Try wiping everything, then reboot recovery, wipe everything again
Then try and flash again
If all else fails try ruu through bootloader, you will still have s off
Sent from my PG86100 using xda app-developers app
donkeykong1 said:
Maybe your sd card is corrupted. Try another card if you have one around
Click to expand...
Click to collapse
It's the same with another SD-card.
hossman said:
What hboot?
Click to expand...
Click to collapse
It's hboot 1.50.5050
The hboot was only changed at the beginning after getting s-off. With this hboot all the ROMs I try now were working before.
However, for the original restore maybe this version could be a problem (hboot 1.58 was on the phone before), but should be no reason for the other ROMs to fail.
Try wiping everything, then reboot recovery, wipe everything again
Then try and flash again
Click to expand...
Click to collapse
Well, this works!
So far I wiped everything but then installed directly the ROM after it without a reboot. No I did like you proposed - wipe, reboot, wipe, flash - and it works again.
Is there a reason why it hasn't worked directly after wiping and needed a reboot between?
If all else fails try ruu through bootloader, you will still have s off
Click to expand...
Click to collapse
Just in case for the next time:
I can only find RUU for Sprint but not VM - do you have a link to a file for a VM phone?
Thanks a lot for the help!
Glad it worked, don't know why but there must have been an issue with recovery
Here is the pg86img I use for vm.
https://db.tt/eBcYZ7yu
Place on root of your sd and rename pg86img.zip
Reboot to bootloader and accept update
This will give you stock Rom and recovery and hboot...s off stays
So if you want to flash again, all you need to do is flash recovery...no unlocking necessary
Sent from my PG86100 using xda app-developers app
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
maybe try this
SockmanTGR said:
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
Click to expand...
Click to collapse
Try Doing a Full Wipe of Your Android System.
Use [TWRP_Recovery_2.7.0.0][Unofficial][quincyatt] Go into factory Wipe > Then Click Advance > Then Wipe Everything but your SD card .
Flash Beanstalk > then Wipe Cache and dalvik > then install PA Gapps > then Wipe Cache & Dalvik again then reboot, Also try installing > Polluti0n's Rom Patch!!
It worked wonders for me , Use Uber kernal & Set Govener to Whetle.
Happy Flashing , Any more Questions Please ask
Joshua Mr PC Repair said:
Try Doing a Full Wipe of Your Android System.
Use [TWRP_Recovery_2.7.0.0][Unofficial][quincyatt] Go into factory Wipe > Then Click Advance > Then Wipe Everything but your SD card .
Flash Beanstalk > then Wipe Cache and dalvik > then install PA Gapps > then Wipe Cache & Dalvik again then reboot, Also try installing > Polluti0n's Rom Patch!!
It worked wonders for me , Use Uber kernal & Set Govener to Whetle.
Happy Flashing , Any more Questions Please ask
Click to expand...
Click to collapse
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
I just Tried it again .
Had No Issues ,
Can You Try with a new SD Card .
Then Do The Wipe
also load TWRP Via Recovery , If You have CWM Go to Install Click > TWRP .
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
Have you vot the right TWRP? One wont work on KK
If you are getting a status 7, your recovery needs updating.
Are you formatting your system?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Put on SD Card and install
captemo said:
Have you vot the right TWRP? One wont work on KK
If you are getting a status 7, your recovery needs updating.
Are you formatting your system?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
This is the one that works for KK
[TWRP_Recovery_2.7.0.0][Unofficial][quincyatt]
Alright i managed to fix the damage but i'm back to beanstalk with cwm. (i had to go through cyanogenmod and put it on using rom manager)
I'm still getting the bugs though(as far as I can tell. I've had one reboot already)
CWM is now functioning normally.
You mentioned a kernel? How would I go about that? I'm still relatively new to rooted devices. So please provide a detailed step-by-step information if you can.
SockmanTGR said:
Alright i managed to fix the damage but i'm back to beanstalk with cwm. (i had to go through cyanogenmod and put it on using rom manager)
I'm still getting the bugs though(as far as I can tell. I've had one reboot already)
CWM is now functioning normally.
You mentioned a kernel? How would I go about that? I'm still relatively new to rooted devices.
Click to expand...
Click to collapse
you can go to the Original Development thread and find the thread for the Uber kernel. pay attention cause one is for JB and the other for KK. whichever Beanstalk your running get the right kernel.
you will flash it just like you flash a rom, or more like you would flash the gapps. you don't have to start over flashing rom again, you are just flashing the kernel to it.
the reboots sound a bit off to me as if you are flashing completely clean, KK is very stable for me and most others. maybe try flashing rom twice as you can get 2 different reactions on 2 different flashes.
flash rom
flash rom again
gapps
boot and wait
reboot
go back and flash your kernel
make sure you get all your wipes in middle of all this.
25625292 7345
captemo said:
you can go to the Original Development thread and find the thread for the Uber kernel. pay attention cause one is for JB and the other for KK. whichever Beanstalk your running get the right kernel.
you will flash it just like you flash a rom, or more like you would flash the gapps. you don't have to start over flashing rom again, you are just flashing the kernel to it.
the reboots sound a bit off to me as if you are flashing completely clean, KK is very stable for me and most others. maybe try flashing rom twice as you can get 2 different reactions on 2 different flashes.
flash rom
flash rom again
gapps
boot and wait
reboot
go back and flash your kernel
make sure you get all your wipes in middle of all this.
Click to expand...
Click to collapse
I followed your instruction with the kernel(http://forum.xda-developers.com/showthread.php?t=2326786) Had to download it directly to my phone. It didn't like it from my laptop.
Successfully installed.
I'll let you guys know if my problem continues,
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
You are not using twrp from the thread linked. Also do NOT use the twrp app for the recovery as my recovery is not found there. It can only be found in my thread. Flash it in recovery & you're good to go.
SockmanTGR said:
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
Click to expand...
Click to collapse
i had the same problem and went to liquid smooth and is stable
jemsTV said:
i had the same problem and went to liquid smooth and is stable
Click to expand...
Click to collapse
If you like beanstalk try this fix. New problem I'm getting a lot of graphical bugs now. So far just in browser but everything flickers including system ui
SockmanTGR said:
If you like beanstalk try this fix. New problem I'm getting a lot of graphical bugs now. So far just in browser but everything flickers including system ui
Click to expand...
Click to collapse
If you are using Beanstalk you should probably read the BeanStalk thread, both of these common problems (screen flicker and failure to wake) are solved with a Aroma package made by p0llution. You flash it in recovery and all is good. Link is in 1st post, right next to ROM link. You can also switch kernels and boot animations with same package.
delawaredrew said:
If you are using Beanstalk you should probably read the BeanStalk thread, both of these common problems (screen flicker and failure to wake) are solved with a Aroma package made by p0llution. You flash it in recovery and all is good. Link is in 1st post, right next to ROM link. You can also switch kernels and boot animations with same package.
Click to expand...
Click to collapse
Would I need to reflash the ROM to ally another kernel?
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
As instructed, you need to do some reading. In my last post I gave you instructions on how to add kernel.
Help yourself first, then others will be more than happy to assist.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
I'll give you some slack 'cause I am still close enough to my first flash that I remember being full of questions, but at least read the OP and most recent pages in your ROM thread. You should skim through it all ideally but some are 100+ pages so....
Kernel switching in general does not require any ROM action, there are likely cases that it might be useful but I've never had a problem. You will need to ensure that the kernel is matched to your ROM; KitKat or Jellybean or whatever. I usually do it as I flash a ROM but I have gone back and installed a kernel on a running ROM plenty of times; Uber for instance was released after I had BeanStalk up and running, it is a good kernel so I switched to that.
As a more general point the Note is hard to brick, as long as you don't somehow mess up the recovery (CWM or TWRP) you are just a quick restore away from back to normal. Use the backup function in your recovery, it is your friend and savior. Keep a copy of the back-up on your PC (or Mac) and you will usually be golden.
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
If you are on BS Rom you should know that all you need to to know is on the OP post-the rom and the patch. The latter contains about 5 different kernels which you can switch betw. to your hearts content. The patch is n00bie proof to make your switches. Really hit BS OP.
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
Just like all the other kind gents adv'd, it's all in patch's OP:
http://forum.xda-developers.com/showthread.php?t=2535857
Including polluti0n's patches thread:
http://forum.xda-developers.com/showpost.php?p=50529734&postcount=854
He uses aroma installer, so when you flash it (personally, I did it with CWM) you don't need to wipe cache/dalvik nor wipe phone, he mentons this on patch's thread while answering questions I believe. The screenshots show you some differences between the kernels he has available, either CM, Uber or PAC.
Personally, I'm using PAC since for me it seemed to work better with the Xposed's Netflix workaround, whereas it didn't work that well with Uber.
Also, the patch provides fixes, for camera, screen flicker and such.. Give it a try, and you'll definitely love your phone more!
So I found another thread like this but couldn't seem to find an answer. I am new to rooting and wanted to put the viper rom on my phone. But after I install it the phone just keeps rebooting, it will get to viper and then flash my lockscreen and go straight to a reboot. So steps I did to get the rom.
First I went to fast boot and fastboot flash boot boot.img. Then I went into recovery (I have 4ext) activated smart flash and factory restored/wiped my phone. Lastly I installed the zip file from recovery window. I have s-on but that shouldn't matter the way I did it right? I am not sure I did everything right but I have done smooth criminal on my phone and that worked fine, just that my wifi radio stopped working which is weird. Any help would be appreciated I am a noob =]
tyscof said:
So I found another thread like this but couldn't seem to find an answer. I am new to rooting and wanted to put the viper rom on my phone. But after I install it the phone just keeps rebooting, it will get to viper and then flash my lockscreen and go straight to a reboot. So steps I did to get the rom.
First I went to fast boot and fastboot flash boot boot.img. Then I went into recovery (I have 4ext) activated smart flash and factory restored/wiped my phone. Lastly I installed the zip file from recovery window. I have s-on but that shouldn't matter the way I did it right? I am not sure I did everything right but I have done smooth criminal on my phone and that worked fine, just that my wifi radio stopped working which is weird. Any help would be appreciated I am a noob =]
Click to expand...
Click to collapse
Did you wipe all partitions except SD card before flashing?
donkeykong1 said:
Did you wipe all partitions except SD card before flashing?
Click to expand...
Click to collapse
I flashed the boot img and then wiped then flashed the zip, I didn't do format all except sd card though I just did wipe data/factory reset ill try that
donkeykong1 said:
Did you wipe all partitions except SD card before flashing?
Click to expand...
Click to collapse
Well I tried that and it looks like it continues to reboot over and over
tyscof said:
Well I tried that and it looks like it continues to reboot over and over
Click to expand...
Click to collapse
In ROM thread it says if you have problems flashing, go to recovery and flash ROM again. So try that, don't wipe anything, just flash zip and see if that helps
donkeykong1 said:
In ROM thread it says if you have problems flashing, go to recovery and flash ROM again. So try that, don't wipe anything, just flash zip and see if that helps
Click to expand...
Click to collapse
Well Ive tried to install it a bunch of different times now, do you think double installing it will change something?
tyscof said:
Well Ive tried to install it a bunch of different times now, do you think double installing it will change something?
Click to expand...
Click to collapse
Maybe. It did the trick for me bunch of times. No harm in trying, right?
donkeykong1 said:
Maybe. It did the trick for me bunch of times. No harm in trying, right?
Click to expand...
Click to collapse
Well I tried it a few times but didnt work. =/ darn
I tried messaging viper the guy who posted the lastest update on here but I doubt he will get back to me, any other suggestions? Does it have to do with a kernal or something?
tyscof said:
Well I tried it a few times but didnt work. =/ darn
Click to expand...
Click to collapse
Did you check md5sum when you downloaded the ROM? Maybe the zip is corrupted
donkeykong1 said:
Did you check md5sum when you downloaded the ROM? Maybe the zip is corrupted
Click to expand...
Click to collapse
No I havent but I have tried two different zips so I doubt that is it
Try some other ROM. If the phone boots fine, try Viper again, but don't flash boot.img before, just wipe and flash from recovery. And make sure smartflash is turned on