Just wiped everything and flashed with Amon RA's recovery straight to FRF83. My phone has rebooted about 7 times over the few hours I've had it. Anyone else experiencing this?
Radio is 4.06.00.12_07.
I went from [email protected]'s FRF50 ROM to his FRF83 using the latest AmonRA. I wiped cache and Dalvik before flashing the zip just to be safe. Aside from it freezing on first boot at the lock screen (battery pull fixed it), I've been good.
Can you link me to his ROM? I had a reboot during first long boot. Freaking annoying!
I went with #2, which is rooted with superuser already installed.
http://android.modaco.com/content/g...-frf83-stock-rooted-deodex-superboot-repacks/
Wiped and flashed that one and I'm still getting reboots. Anyone else have any ideas?
Sent from my Nexus One using XDA App
rickytenzer said:
Wiped and flashed that one and I'm still getting reboots. Anyone else have any ideas?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yes, stop using leaked software and wait for final release.
I'm worried that we're close enough to the OTA that I'll still have these issues when it hits...
Could this be a precautionary thing the phone is doing because of battery temp? Right now it's at 36°C. Is that normal?
Try to boot the phone without the SD card. Good luck!
I had this issue as well but I was also running an overclocked kernel. After I flushed everything (post backup w/ titanium backup) I flushed, reflashed rom, kernel and other mods and I was good to go.....
Alright I did a little digging now that I'm home and have access to ADB.
I pulled the last_kmsg:
http://pastebin.org/362745
I'm no genius but I'm pretty sure that "ARM9 has CRASHED" is NOT a good thing. Also, logcats show noting unusual prior to the reboots.
Anyone know what the frig is going on?
Thanks!
EDIT: I'm using the [email protected] #1 kernel which I assume is the stock kernel for FRF83.
I've had a few "reboots" but they weren't reboots in the traditional sense. Or the reboot seemed to happen VERY fast, maybe in less than 10 seconds, rather than 30 or 40 that it normally would. So i'm not quite sure what to call it but it is annoying..
Please kernel gurus! Hellllllp!
Related
What is happening? Pulled battery 5 times already today...what should I do and would pulling battery as often as this affect my phone or battery?
-------------------------------------
Sent via the XDA Tapatalk App
Anyone?
-------------------------------------
Sent via the XDA Tapatalk App
What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
Click to expand...
Click to collapse
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
Click to expand...
Click to collapse
I did wipe prior flashing to Paul's zip with radio.
-------------------------------------
Sent via the XDA Tapatalk App
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
SurfHost said:
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
Click to expand...
Click to collapse
does it work?
Im having similar issues with my 2.2 installation. I have it installed on my wife's non-rooted N1.
Not just that but the market is not even usable. Even if I clear cache.
Again, her phone is not rooted, I wipped everything from her phone then applied Froyo and its been a nightmare. Her phone isn't even stable enough to use and I cant seem to figure it out.
I need to find a way back to 2.1 without having to root her phone. She is adamant about me not doing that to her phone even though Ive rooted all the phones I've ever used with no issues.
I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Ive tried all that on her phone. I just wiped it again completely and re flashed just in case that was the issue. Phone still had all the issues described in this thread.
I wiped the sd card, wiped all previous system files via the stock recovery and re flashed the update zip. You cant get anymore clean than that and its still so unstable the phone its unusable. I have to either hope soft booting works or pull the battery as a last ditch.
Is there any way I could downgrade her phone to 2.1 without rooting? I tried the shipping rom in the sticky above but it seems that isn't totally legit for stock use because the phone doesn't like how its signed.
I guess I could call google/htc tomorrow but who knows where that'll get me. The only bonus iud that her phone is not rooted so she didn't really have her warranty voided.
-------------------------------------
Sent via the XDA Tapatalk App
I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Click to expand...
Click to collapse
I was worried if I was the only one with this problem. Phone improved today (3rd day of using) but I didn't do anything to it. Only hanged once when someone called. Hanged on calling in screen and had to pull battery.
Only once compared to 7 times yesterday!
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
does it work?
Click to expand...
Click to collapse
Yes until now it does. Sometimes the power button is reacting a little late but i havent had to pull the battery yet with the older radio.
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
krabman said:
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
Click to expand...
Click to collapse
I'll give this a shot when I get home from work. I'll report back on if it works or not. Thanks for the idea.
Interesting, not that I'm complaining, but after a few days of using 2.2 it seems more stable now....? haven't had any freezes today...yet.
Power button response also getting better.
-------------------------------------
Sent via the XDA Tapatalk App
I haven't had any issues for a few days as well. Still wondering if it had to do with the battery level.
-------------------------------------
Sent via the XDA Tapatalk App
SurfHost said:
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Older radios are not 100% compatible.
Being the noob I am, I can't post this question in the dev forum. Does anyone know if Liberty is compatible with safestrap or not? I know the official instructions says CWM only, but I have read that many install using safetstrap without any problems.
That said, I for the life of me can't get it to boot after install. Are there any special tricks to get it to work with safestrap? Being a noob to Android (this D3 is my first foray into Android), I would like to stick with safestrap until I am very comfortable since it is rather idiot-proof. Thanks!
uconnjack said:
Being the noob I am, I can't post this question in the dev forum. Does anyone know if Liberty is compatible with safestrap or not? I know the official instructions says CWM only, but I have read that many install using safetstrap without any problems.
That said, I for the life of me can't get it to boot after install. Are there any special tricks to get it to work with safestrap? Being a noob to Android (this D3 is my first foray into Android), I would like to stick with safestrap until I am very comfortable since it is rather idiot-proof. Thanks!
Click to expand...
Click to collapse
The thread at RootzWiki in the dev section for Droid3 is very helpful.
Some of the things to double check:
- Make sure you're swapping to "safe mode" before flashing the .zip
- Wipe data/cache
It works fine with safestrap
Sent from my DROID3 using xda premium
I have been switching to safe mode, clearing data/cache, rebooting, installing the ROM zip (with no apparent errors), clearing data/cache again, and then trying to boot the ROM, but it just hangs on a blank screen for >20 minutes before I pull the battery. Tried this a few times, even redownloading the zip, but its always the same.
Steel Droid and Maverick have worked fine, but just can't seem to get Liberty to work. I have reviewed and seacrhed the forums, inluding rootwiki, hoping there was some special trick that needed to be done with this specific ROM, but have found nothing.
Maybe I will try installing an older Liberty ROM to see if that works' and also maybe reinstalling safestrap, maybe even rerooting.
Any ideas?
Sent from my DROID3 using Tapatalk
uconnjack said:
I have been switching to safe mode, clearing data/cache, rebooting, installing the ROM zip (with no apparent errors), clearing data/cache again, and then trying to boot the ROM, but it just hangs on a blank screen for >20 minutes before I pull the battery. Tried this a few times, even redownloading the zip, but its always the same.
Steel Droid and Maverick have worked fine, but just can't seem to get Liberty to work. I have reviewed and seacrhed the forums, inluding rootwiki, hoping there was some special trick that needed to be done with this specific ROM, but have found nothing.
Maybe I will try installing an older Liberty ROM to see if that works' and also maybe reinstalling safestrap, maybe even rerooting.
Any ideas?
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
Check the MD5, mine kept doing that until I downloaded over 3g. Downloading over 3g finally gave me an MD5 match
Sent from my DROID3 using xda premium
I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.
Lyxdeslic said:
I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.
Click to expand...
Click to collapse
It has a different way of reporting battery usage, it doesn't affect it though (based on 5.6.890) I've had my phone on for 9 hours now, medium usage, and I'm at 86%.
Lyxdeslic said:
I flashed Liberty 2.0 with Safestrap, two days ago. First reboot after flashing led to the phone hanging on the spinning eagle boot-up animation. I booted into recovery, wiped data, formatted, and re-flashed, and it worked fine during that boot-up. However, boot-up times are strange, and there's usually a blank black screen when booting up for about 10-15 seconds for me prior to the boot animation showing up.
On a side note, my battery life with Liberty 2.0 is horrendous. Phone Idle = 36%, Cell Standy = 39%, Android OS = 3%, Wifi = 2%. I don't get it. Haven't really downloaded any apps at all yet.
Click to expand...
Click to collapse
If flashing from the last version of Liberty there shouldn't be a need to wipe, I didn't anyway. It took quite a while, more than 5min, to finally boot just after flashing. As far as the 10-15 second delay, that is how safestrap works. 10 seconds at the safestrap splash screen and about 10 seconds of black before the bootanimation. Though I'm not sure of why the later takes so long. For me the previous version of Liberty took just as long to boot.
Yup, that was it, the MD5s would not match up until I downloaded over 3g. Wireless or PC->phone would always have mismatched numbers. I didn't check the Steel Droid or Maverick ROMS I downloaded wirelessly, but those installed fine regardless. Wonder why the consistent download errors for the Liberty ROM?
Thanks for your help!
uconnjack said:
Yup, that was it, the MD5s would not match up until I downloaded over 3g. Wireless or PC->phone would always have mismatched numbers. I didn't check the Steel Droid or Maverick ROMS I downloaded wirelessly, but those installed fine regardless. Wonder why the consistent download errors for the Liberty ROM?
Thanks for your help!
Click to expand...
Click to collapse
I don't know why either I figured it was my router having a moment, but you're the second other person I've helped with that.
eww245 said:
If flashing from the last version of Liberty there shouldn't be a need to wipe, I didn't anyway. It took quite a while, more than 5min, to finally boot just after flashing. As far as the 10-15 second delay, that is how safestrap works. 10 seconds at the safestrap splash screen and about 10 seconds of black before the bootanimation. Though I'm not sure of why the later takes so long. For me the previous version of Liberty took just as long to boot.
Click to expand...
Click to collapse
If you want to use the new lockscreens or themes you'll need to preform a data wipe, Kejar said so himself.
Androidsims said:
I don't know why either I figured it was my router having a moment, but you're the second other person I've helped with that.
If you want to use the new lockscreens or themes you'll need to preform a data wipe, Kejar said so himself.
Click to expand...
Click to collapse
Using ring lockscreen, haven't tried any of the themes though. I'm suprised it did work actually.
I'm running it with safe strap right now not the best battery life but it'll do til hash gets ics running (which I know he will cm7 is my favorite but need tethering and camera)
Sent from my DROID3 using Tapatalk
My md5 sum is correct and I've cleared the data/cache but I only get a black backlit screen for 20 min + til I remove the battery. Anyone got a tip of what to do?
Sent from my DROID3 using XDA App
kAmaOn said:
My md5 sum is correct and I've cleared the data/cache but I only get a black backlit screen for 20 min + til I remove the battery. Anyone got a tip of what to do?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
SBF back to stock 5.6.890, reroot, reinstall safestrap, re-do EVERYTHING pretty much. Thats my solution to everything.
WOW! HOLY CRAP THIS PLACE IS DEAD! Its been a while since I read around these Zio places. Yup, my ol Zio still bootlooped (its around here somewhere). I tried all the "guides" n zip's and skd's and all that other.....stuff, its koo gathering and installing stuff and gettin that lil rush of hope, but then one lil thing goes wrong or ain't in the step-by-step guied, BOOM- all bad, and nobody's around all of a sudden. Alot of HERE, TRY THIS POST FROM SO N SO (not for the Zio), GO TO BLAHBLAH.COM install that n profit (evil setup to rom someone's phone AND wipe it clean), BUT ITS ALL MY BAD, NEWBIE like me shouldn't mess with roots n roms. Don't get me wrong, if I can find somebody that would fix it for cash, id go back to my zio and chuck this HALLWIE A2 (whatever its called) to a dev. Well, I'm probly gona get smashed for posting this. DEEEEP BREATH........K, I FEEL BETTER NOW.
Now I'm soo broke I cant even pay attention!
What you need help on? Bootloop fix? I can help you. Pm me on the details. Could you still get into faatboot or recovery? What service sprint or cricket!?
Sent from my Zio using XDA App
My zio is messed up too. I have no home/launcher or whatever you wanna call it. I can't get to settings to enable usb debugging either so none of the adb stuff works for me (so far). New to this and I don't want to buy another phone just yet. More details can be provided as to how this happened if needed. ty.
Not sure where it is but there was a fast boot zip of launcher apk. If you boot your phone into fast boot and cwm copy the zip to the phone and then flash the zip to your Zio it should resolve the issue
Sent from my Zio
Krsmqn said:
My zio is messed up too. I have no home/launcher or whatever you wanna call it. I can't get to settings to enable usb debugging either so none of the adb stuff works for me (so far). New to this and I don't want to buy another phone just yet. More details can be provided as to how this happened if needed. ty.
Click to expand...
Click to collapse
I can make a launcher apk. flashable zip for ya,just let Me know.
Sent from my LG-P509 using xda premium
openZIO Rom issue
Hi, I just installed the openZIO 2.1.2 ROM. Everything worked fine, but after rebooting and going through the initial set up (i.e. the google user setup blahblah) the VTL Launcher continually force closes and I can't do anything but go back and recover my original boot.img has anyone else had this kind of issue? Any possible fixes? Any help would be appreciated, I know not to many people are in using the Zio forums anymore... but yeah.. Thanks in advance
Try Reflashing again
Sent from my LG-P509 using xda premium
I've actually already done that, and it's still doing the same thing. I've deleted and re-downloaded the ROM, and re-flashed it to my phone, and still having the same issue. VTL Launcher just continually force closes, and it sucks cause I've been waiting months to get to install the ROM cause I couldn't afford a new USB cord. I've read so much on this ROM and everything for the Zio and was excited to actually be able to overclock my phone, and get some pretty good performance boosts out of it. Now I got one, and can't get it to work.. what a sad day
Could you explain your steps when flashing?
Sent from my LG-P509 using xda premium
well I first move the .zip to the sd, then power down and boot up CWM, and "install from SD card" and once it's finished flashing, I reboot the phone. when it comes back up my kyocera logo comes back up and it takes me through the first-boot programming (google sign-in) and once I input my un/pw and sign in, it tells me that VTL had an error and must hit force close. and once I hit force close it continues to come up saying the same thing over and over again. so I rebooted my phone, still the same thing. SO I go back through and flash it back to my original boot.img. I have gone through and completely deleted the openZIO 2.1.2.zip file and re-downloaded it, and gone through the same steps to see if maybe it was just a bad file somehow. But to no avail, still having the same issues.
After you boot into cwm : wipe cache partition, then go into mounts and storage, format: system, data, cache :then go into advanced and wipe dalvick cache.
Now flash rom
Sent from my LG-P509 using xda premium
Ok just went through with what you had mentioned, and still getting the same results. "Sorry! The application VTL.Launcher (process android.process.acore) has stopped unexpectedly. Please try again. with the only option to force close. As soon as I force close, the same message pops up
Have you tryed flashing my rom?
I would try that, and see what happens.
You can always push a launcher with adb or Droid commander.
Sent from my LG-P509 using xda premium
doing this now actually.. been reading for the last hour or so and seems like you did some good work on the ROM. it's flashing now, hopefully all works well I'm excited to see how it goes.
Well it flashed and well... seems to be having a strange issue.
When switching screens, it seems to glitch out? Like you see the icons, and when you switch screens, it's like the icons move but it freezes different frames. imma re-flash it in the morning to see if that helps any.
XCmaster said:
doing this now actually.. been reading for the last hour or so and seems like you did some good work on the ROM. it's flashing now, hopefully all works well I'm excited to see how it goes.
Well it flashed and well... seems to be having a strange issue.
When switching screens, it seems to glitch out? Like you see the icons, and when you switch screens, it's like the icons move but it freezes different frames. imma re-flash it in the morning to see if that helps any.
Click to expand...
Click to collapse
Im outta suggestions, I think you might have a hardware problem, but can't be for sure on that.
I've never heard of anybody having that problem, let me know if you get the issue resolved
Sent from my LG-P509 using xda premium
could defiantly be, this phone is well over a year old and has been dropped quite a number of times lol.
XCmaster said:
could defiantly be, this phone is well over a year old and has been dropped quite a number of times lol.
Click to expand...
Click to collapse
Was your phone acting like that before you flashed openzio?
Sent from my LG-P509 using Tapatalk 2
Nope, I've never had these issues before. And I can still flash it back to my original boot.img and it works like before. I've never had any problems with it, so that's why I'm surprised this is happening lol
XCmaster said:
Nope, I've never had these issues before. And I can still flash it back to my original boot.img and it works like before. I've never had any problems with it, so that's why I'm surprised this is happening lol
Click to expand...
Click to collapse
I guess then its probably not a hardware issue.. hmm.. its almost Like the roms your flashing are getting corrupted some how.
Sent from my LG-P509 using Tapatalk 2
hmm.. .well maybe I'll format my sd and do a factory reset on the phone first, then try to flash the rom?
OK so I just recently wiped and reflashed this rom again and all went well. I've reinstalled a bunch of my apps and all of a sudden I'm getting reboots! Load into os and right away it seems very bogged down....none of my widgets are loading and about 1-2 mins later, I reboot... frustrating.
If its an app is there a way to tell which one and remove it? Or has something pooched the os already? Frustrating this has happened already after a fresh wipe n flash and I couldn't even do a Android backup as it too was having problems (posted that elsewhere).
Aside from this specific prob is there an app or way to find out what program or service is causing a crash or failure to help solve similar issues?
Sent from my SGH-I897 running SGSICS 4.0.3 rc4.2&Glitch kernel v14 b5
Until you get os running better the 2nd link won't help...
http://wiki.cyanogenmod.com/index.php?title=Logcat
http://www.appbrain.com/app/catlog-logcat-reader/com.nolanlawson.logcat
pc103 said:
Until you get os running better the 2nd link won't help...
http://wiki.cyanogenmod.com/index.php?title=Logcat
http://www.appbrain.com/app/catlog-logcat-reader/com.nolanlawson.logcat
Click to expand...
Click to collapse
Logcat is good, but just remember, you will need to set a relatively low rate for number of lines to write to SD to have a chance of catching the crash in the act
Hey guys, I was running Maximum overdrive v1.0 and beastmode 56.8 kernel (no tweaks) when my phone starts freezing and rebooting. It would happen often and even at times It wouldn't boot completely I would have to remove the battery for It to boot. Then It started to get "kernel panic ulpoad mode" I odin flashed back to stock MM but same issues going on. Any ideas? Or its time for a new phone? Thank you
Sent from my SM-N910T using Tapatalk
carmona_sc said:
Hey guys, I was running Maximum overdrive v1.0 and beastmode 56.8 kernel (no tweaks) when my phone starts freezing and rebooting. It would happen often and even at times It wouldn't boot completely I would have to remove the battery for It to boot. Then It started to get "kernel panic ulpoad mode" I odin flashed back to stock MM but same issues going on. Any ideas? Or its time for a new phone? Thank you
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I was curious cause I never heard of that , and some people said a factory reset solved the problem . However a fresh Odin install is good. Did you wipe system as well as the normal wipes?
Bubba Fett said:
I was curious cause I never heard of that , and some people said a factory reset solved the problem . However a fresh Odin install is good. Did you wipe system as well as the normal wipes?
Click to expand...
Click to collapse
Yes I did, and nothing seemed to work, even went back to stock 5.1 and same issues consist.
Sent from my SM-N910T using Tapatalk
carmona_sc said:
Yes I did, and nothing seemed to work, even went back to stock 5.1 and same issues consist.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yikes. I didn't even see a ton of info on the subject. I can't imagine there is anything left on the device to cause any issues. Hopefully someone with more knowledge about this sees this post. Note 7 release party Aug 2nd if it comes to that!
same issue i see alot of people with it, its the emmc i confirmed it beause yesterday while i was alseep my emmc decided to give up on life no recovery no download failed to read emmc, the problem is repairing it im not gonna take it to samsung as they will charge almost the price of a new phone i have found a chip for it but it says it has sm n910p/f firmware on it not sure if it would be an issue as i could reflash the tmobile firmware on it.
http://www.aliexpress.com/item/Bran...2630152207.html?spm=2114.40010708.4.13.nPWCQ2
any advice on the chip?
So, what was the final solution?