has stopped unexpedectly.
i was messing around with switching the ROMS and when i rebooted, it said this.
i have no home screen, and it keeps popping up but i can still recieve phone calls and texts
anyone have any idea of what to do?
i can't seem to go into recovery mode either..
pacDiesel said:
has stopped unexpedectly.
i was messing around with switching the ROMS and when i rebooted, it said this.
i have no home screen, and it keeps popping up but i can still recieve phone calls and texts
anyone have any idea of what to do?
i can't seem to go into recovery mode either..
Click to expand...
Click to collapse
nothing to worry about.. if you switched radio, check that the time on the phone is correct, sometimes its being reset to year 1903 which messes up many apps. Also if you switched radio/spl did you run fastboot erase system -w afterwards?
This exception should not be related to the recoveryconsole
easiest is just to wipe everything and reflash, dont forget ext. if youve used it.
If recovery is for some reason unaccesable you can reflash via flash_image() when the phone has booted android.
Also do a logcat
Mod. edit: not dev related, moved to general
ivarson_swe said:
nothing to worry about.. if you switched radio, check that the time on the phone is correct, sometimes its being reset to year 1903 which messes up many apps. Also if you switched radio/spl did you run fastboot erase system -w afterwards?
This exception should not be related to the recoveryconsole
easiest is just to wipe everything and reflash, dont forget ext. if youve used it.
If recovery is for some reason unaccesable you can reflash via flash_image() when the phone has booted android.
Also do a logcat
Click to expand...
Click to collapse
Yeah bro, I have no idea what you just said.
lol
nothing to worry about.. if you switched radio, check that the time on the phone is correct, sometimes its being reset to year 1903 which messes up m
Click to expand...
Click to collapse
Yeah bro, I have no idea what you just said.
lol
Click to expand...
Click to collapse
Which rom were you using and which rom are you using now. Did you change your radio or spl before installing this rom.
Load up into recovery and run fix uid mismatches. Reboot and see if that helps.
Does your app launcher work? If so run terminal emulator. Type in su and then enter
Type in fix_permissions and then enter. Let the script run.
Type I'm exit then enter
Type in exit and then enter again. Terminal will close. Reboot phone. If you cannot get to terminal emulator then run it from adb ( if possible )
And the other poster was referring to when you change radios there are a few commands. He wanted to make sure you ran them all
-------------------------------------
Sent via the XDA Tapatalk App
Related
OK,
so my phone just rebooted itself after happily sitting on my desk for hours.
It's now stuck on the HTC logo....
I pulled the battery, and it's doing the same thing.
I literally have done nothing to my phone all day...
Luckily I have a nandroid backup, but ???
Has anyone else seen anything like this ?
grifforama said:
OK,
so my phone just rebooted itself after happily sitting on my desk for hours.
It's now stuck on the HTC logo....
I pulled the battery, and it's doing the same thing.
I literally have done nothing to my phone all day...
Luckily I have a nandroid backup, but ???
Has anyone else seen anything like this ?
Click to expand...
Click to collapse
OK. F**K
Now I'm concerned.
Tried to boot into recovery, and all I see is
Build : RA-heroc-v1.6.2
on the bottom of the screen, and nothing else.
Can you access the shell via usb? Can you boot into recovery?
This happened to me after a flash without wipe.
Let us know how it goes - I hope you haven't any hardware issues!
Sent from my MatrixROM using the XDA mobile application powered by Tapatalk
I can access via shell.
It looks like it's in recovery, but there's no menu on the phone.
And there wasn't any other funny stuffs aside from changed firmwares (ie. recent overclock finds, etc)?
I'd try to wipe and restore via usb shell. It's sounding like you've some more funk going on...
Sent from my MatrixROM using the XDA mobile application powered by Tapatalk
grifforama said:
OK,
so my phone just rebooted itself after happily sitting on my desk for hours.
It's now stuck on the HTC logo....
I pulled the battery, and it's doing the same thing.
I literally have done nothing to my phone all day...
Luckily I have a nandroid backup, but ???
Has anyone else seen anything like this ?
Click to expand...
Click to collapse
What rom are you running? I notice my internet is very laggy as of last night and I had been charging via usb and the debugging icon did not go away when I unplugged it. Running Flips 2.1d.
AboveUnrefined said:
And there wasn't any other funny stuffs aside from changed firmwares (ie. recent overclock finds, etc)?
I'd try to wipe and restore via usb shell. It's sounding like you've some more funk going on...
Sent from my MatrixROM using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Trying to restore via ADB now, not looking good.
How do you wipe via adb ?
chubbzlou said:
What rom are you running? I notice my internet is very laggy as of last night and I had been charging via usb and the debugging icon did not go away when I unplugged it. Running Flips 2.1d.
Click to expand...
Click to collapse
Running Fresh 2.1d
I haven't done anything weird to it at all....it was just sitting there on my desk doing nothing.
Off the top of my head I don't know what dirs to clear or if you can just do a 'wipe'.
Anybody else know? I'm at work so I'm limited...
Also - is your battery healthy?
Sent from my MatrixROM using the XDA mobile application powered by Tapatalk
Is your phone on? If so you can go to setting privacy and hit factory data reset then hit reset phone. But I think this erases you sdcard also. Remove your sdcard just incase. Hope this helps.
Battery healthy
Attempting to restore via ADB using this guide
http://forum.xda-developers.com/showthread.php?t=614016
Gets here and then no further
nandroid-mobile v2.2.1
touch: /cache/recovery/log: No such file or directory
Using G1 keyboard, enter a directory name substring and then <CR>
to find matches or just <CR> to accept default:
chubbzlou said:
Is your phone on? If so you can go to setting privacy and hit factory data reset then hit reset phone. But I think this erases you sdcard also. Remove your sdcard just incase. Hope this helps.
Click to expand...
Click to collapse
Not really
I can't get past the HTC logo.
Boot into recovery on your phone.. Yes I know you cant see the menu.
But on your computer type.
adb remount
adb shell
u
Just the letter u.. It should bring up recovery on your computer.
when I do that, it doesn't look like RA Recovery ?
I only see this ?
C:\AndroidSDK\tools>adb shell
/ # u
u
←[H←[JMore Utilities by BKMO
[1] Convert ext3 > ext4 no data loss
[2] Fix Permissions 2.03 experimental
[3] Backup APPS on ext to FAT32
[4] Restore APPS from FAT32 to ext
[5] Partition SD 3 partitions (can set sizes)
[6] Fix auto-rotate problems
[7] Run BART 1.0.1 Backup
[8] Run BART 1.0.1 Restore
[9] Reset/delete Battery Stats
[q] Quit to Console Prompt
Boot me out of here! (reboot)
[r] Return to Recovery Menu
Enter Number>
Resorted to trying to go back to Stock via RUU.
Managed to get to the other recovery screen (HBOOT??)
Looks like I may be OK...just have to go though the whole root thing again
Ohh yea.. I used it for the apps thing. I was thinking it had wipe factory and dalvik
grifforama said:
Resorted to trying to go back to Stock via RUU.
Managed to get to the other recovery screen (HBOOT??)
Looks like I may be OK...just have to go though the whole root thing again
Click to expand...
Click to collapse
I can get to that screen all the time. Iv even factory reset from there.. You dont lose root if you do reset.
Try that and then try bringing up custom recovery.. If it doesnt work, download and flash the recovery again. Maybe it got corrupted some how.
This has been happening to me for the past few days (minus the stuck at boot screen)
After a few hours, my phone would just randomly restart. This has happened about 3 or 4 times in the past couple days.
Yesterday it happened and when it turned back on, I got the "Damaged SD Card" message and I had to format
So I formatted it and reflashed the ROM and it seems fine now.
I'm running DamageControl v2.07.2
That definitely sounds like what's going on. I'd replace the sd card - they do flake out...
Sent from my MatrixROM using the XDA mobile application powered by Tapatalk
Back to Stock
Had Nandroid
Had to wipe
Ok my battery was draining at a faster rate than normal so i figured I'd reboot my phone. Once I shut down my phone and hit the power button it boot into fastboot mode. I am literally the most basic Nexus 4 user meaning, I've never rooted, unlocked, flashed or done anything to my phone. I simply just don't know how to do any of this stuff so it's not like I was tinkering with anything.
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode. I honestly have no clue what went wrong. Again, I know nothing about root and stuff but there must be a solution right or am I the first person to ever brick their completely stock phone by trying to restart it? I figure some of the awesome people on here what know what to do or to simplify some steps to fixing this. Thanks in advance.
Sounds like your volume down key might be stuck (as holding that when you power on is how you get to fastboot).
If it's not that then maybe you should try downloading the factory image from here: https://developers.google.com/android/nexus/images and letting that install.
I don't think the button is stuck.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
After restoring a factory image, it is recommended that you lock the bootloader, for security reasons.
Click to expand...
Click to collapse
Rusty! said:
Sounds like your volume down key might be stuck (as holding that when you power on is how you get to fastboot).
If it's not that then maybe you should try downloading the factory image from here: https://developers.google.com/android/nexus/images and letting that install.
Click to expand...
Click to collapse
Definitely not the volume down key. I'm able to navigate with volume rocker in fastboot.
Alex_Dreyk said:
I don't think the button is stuck.
Click to expand...
Click to collapse
are u able to get to the bootloader and recovery
One3OneKing said:
Definitely not the volume down key. I'm able to navigate with volume rocker in fastboot.
Click to expand...
Click to collapse
I picked an instrucktion form the link below.
As you have already wiped it do as in instruction
faddyie said:
are u able to get to the bootloader and recovery
Click to expand...
Click to collapse
yes, I can get to recovery. can i get to the bootloader?how would i get there, no clue. lol
Bootloader = fastboot
Try the factory image flash.
Rusty! said:
Bootloader = fastboot
Try the factory image flash.
Click to expand...
Click to collapse
I kind of have an idea of how to do that but a link to a set of instructions would be great. I've looked but most people have rooted and installed computer programs so I didnt know what exactly I would need to do in my completely stock scenario.
One3OneKing said:
I kind of have an idea of how to do that but a link to a set of instructions would be great. I've looked but most people have rooted and installed computer programs so I didnt know what exactly I would need to do in my completely stock scenario.
Click to expand...
Click to collapse
Dear if you have not rooted it. your stock rom has not gone any where...
Goto recovery and then press volume up key and power button. keep holding for like 10 secs and u will be get into the system. However, check that your volume down key is not pressed
faddyie said:
Dear if you have not rooted it. your stock rom has not gone any where...
Goto recovery and then press volume up key and power button. keep holding for like 10 secs and u will be get into the system. However, check that your volume down key is not pressed
Click to expand...
Click to collapse
No luck. This is crazy, I literally don't know what happened...:crying:
Have u downloaded the sender image file as described in previous posts
Sent from my Nexus 4
One3OneKing said:
Ok my battery was draining at a faster rate than normal so i figured I'd reboot my phone. Once I shut down my phone and hit the power button it boot into fastboot mode. I am literally the most basic Nexus 4 user meaning, I've never rooted, unlocked, flashed or done anything to my phone. I simply just don't know how to do any of this stuff so it's not like I was tinkering with anything.
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode. I honestly have no clue what went wrong. Again, I know nothing about root and stuff but there must be a solution right or am I the first person to ever brick their completely stock phone by trying to restart it? I figure some of the awesome people on here what know what to do or to simplify some steps to fixing this. Thanks in advance.
Click to expand...
Click to collapse
Being that you haven't unlocked or rooted the phone its most likely a hardware problem. If you bought it from Google RMA
From my BLACKED OUT N4
Before RMA'ing try the factory image. You don't need instructions, you just run a .bat file while in fastboot. What have you git to lose?
if you wiped your partitions, then you dont have a rom on your phone. flashing the factory img via fastboot would fix that.
simms22 said:
if you wiped your partitions, then you dont have a rom on your phone. flashing the factory img via fastboot would fix that.
Click to expand...
Click to collapse
You can't wipe /system from stock recovery, so he didn't do that.
EvoXOhio said:
You can't wipe /system from stock recovery, so he didn't do that.
Click to expand...
Click to collapse
i havent seen the stock recovery in a loooooooooong time, just going by what he wrote in his post :angel:
heres his quote, and thats what happens exactly when you dont have a rom stalled on the device..
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode
Click to expand...
Click to collapse
simms22 said:
i havent seen the stock recovery in a loooooooooong time, just going by what he wrote in his post :angel:
heres his quote, and thats what happens exactly when you dont have a rom stalled on the device..
Click to expand...
Click to collapse
I'm guessing he wiped data and/or cache. If he truly is stock like he says then he didn't wipe his /system partition.
My phone got messed up once and I couldn't make or restore nandroids nor boot past the CM boot image, and it ended up being because my /data partition got corrupted. No idea how. I had to flash stock Google images to get it to boot. it happened during normal use of the phone.
EvoXOhio said:
I'm guessing he wiped data and/or cache. If he truly is stock like he says then he didn't wipe his /system partition.
My phone got messed up once and I couldn't make or restore nandroids nor boot past the CM boot image, and it ended up being because my /data partition got corrupted. No idea how. I had to flash stock Google images to get it to boot. it happened during normal use of the phone.
Click to expand...
Click to collapse
yea, if had my data partition get corrupted too, wouldnt finish booting. flashing the stock img fixed it quick. but it was my own fault.. bennchmarking at 1890mhz with fsync turned off
I ended up just taking advantage of my warranty and I'll get a new one. Thanks to everyone for the suggestions and tips. I'm still trying to figure out why simply turning off the phone to restart it caused this to happen. It makes no sense.
Hello everybody.
I'm writing in hopes someone can shed any light in a problem I'm having with my phone:
When I try to install an app, I get an error message saying X Not Installed. It happens with every app and every install method (via playstore, sideloading, TiBu restoring...).
Wiping data doesn't work, I still get X Not Installed after a clean wipe. Neither does restoring an older nandroid backup.
The only thing that works is getting a factory image from google and flash the data partitition, after wich I can again install apps for a couple of days until the error starts appearing and I have to repeat the process.
Any and all help would be greatly appreciated.
Hate to say it but it sounds like a hardware failure. When you flash data I'm assuming you mean the userdata.img. That seems to fix it for awhile but then it gets corrupted again. Sounds like the flash memory is going bad. Are you still under warranty?
Sent from my Nexus 5 using XDA Free mobile app
What does the kernel say? I assume it would log something in case of an hardware failure. Root your phone, connect it to your computer, try to install any app and run "adb shell su -c dmesg" in a shell.
First of all, I TYVM for your replies.
jd1639 said:
Hate to say it but it sounds like a hardware failure. When you flash data I'm assuming you mean the userdata.img. That seems to fix it for awhile but then it gets corrupted again. Sounds like the flash memory is going bad. Are you still under warranty?
Click to expand...
Click to collapse
I never thought it might be a hardware problem, but what you say makes sense.
The bad news is I'm not under warranty, and even if I were, I wouldn't even know how to begin explaining the problems to the idiots at my providers customer service, let alone prove to them it was not something I did. I can hear them now blaming me for installing apps on my own in the first place.
The good news is I'm due for an upgrade in september.
Until then I guess I will not be able to install stuff, but the "non-smart" of the phone seems to work ok in the meantime.
Firefrost said:
What does the kernel say? I assume it would log something in case of an hardware failure. Root your phone, connect it to your computer, try to install any app and run "adb shell su -c dmesg" in a shell.
Click to expand...
Click to collapse
Right now I'm in my "good" days after having flashed the userdata.img just this morning. I'm crossing my fingers that this time it lasts a while before it starts giving me grief, but as soon as it does, I'll do what you say and post the results.
Thanks again.
Hey guys,
I keep trying to get PA to work on my phone and every time i install TWRP i get a new issue. Can anyone help me get back to stock so i can go back to CWM and CM11 which seems to be so much better on the G2?
My issue is that after managing to restore the stock OS using download mode i rooted and flashed TWRP, now when i restarted into TWRP i cant seem to get back to the OS. I did do a backup before playing around but it seems i can restore everything apart form data but even then it does not boot it just goes to a blank screen after the LG logo and the notification light is on but nothing else. Download mode is not working it just has the loading download mode icon and that's it.
I managed to push PA and gapps to my phone using adb push and stupidly decided to try that without pushing some back up roms and now after wiping and trying to install PA and gapps anything further i try to push now tells me its read-only through adb, i have tried doing adb remount and that does not work.
When i try to install PA and Gapps they seem to work but when i restart i am just stuck on the LG boot screen.
Please can you help i really have no idea what do to and i have googled around without much help.
My phone is LG G2 int 32gb
Thanks!
You should try to wipe all but internal storage. Then try to restore.
bender_007 said:
You should try to wipe all but internal storage. Then try to restore.
Click to expand...
Click to collapse
Could you please elaborate a bit more? Im new to TWRP and dont know the options by the prompts i get are: Factory reset / Advanced Wipe / Format Data.
I was just worried that i might wipe too much so have always gone with factory reset on TWRP as it says on their site that should be enough:
teamw.in/whattowipe
Should i do an advanced wipe and try again?
Everything but internal. Pictures and your rom etc are on internal . Yes. Factory reset, too. Other options are in advanced wipe
Slashkun said:
Could you please elaborate a bit more? Im new to TWRP and dont know the options by the prompts i get are: Factory reset / Advanced Wipe / Format Data.
I was just worried that i might wipe too much so have always gone with factory reset on TWRP as it says on their site that should be enough:
teamw.in/whattowipe
Should i do an advanced wipe and try again?
Click to expand...
Click to collapse
Go to advanced and select everything except internal.
Sent from my Vs980 running Jackpotclavin's cm11
Lawlrus said:
Go to advanced and select everything except internal.
Sent from my Vs980 running Jackpotclavin's cm11
Click to expand...
Click to collapse
Hey thanks for the help, I have done the advanced wipe and attempted a restore however the data part still fails. I tried to push stuff using ADB again and it is either coming up with a protocol failure and the phone is restarting or it still says read-only file system.
Any other options available? Also what was the advanced wipe supposed to achieve in comparison to the normal one? (just asking as I'm interested in learning about the whole process)
hmm..can you enter twrp ? Just install a new one.
bender_007 said:
hmm..can you enter twrp ? Just install a new one.
Click to expand...
Click to collapse
Hey,
I'm in TWRP and that works but what do you mean by install a new one, the only Rom option i have is the PA rom i put on the phone that does not seem to do anything and the backup i had that again does not seem to do anything
Twrp 2.7? Wipe all except internal. Factory reset, too. Try downloading some other rom and push it via adb.
bender_007 said:
Twrp 2.7? Wipe all except internal. Factory reset, too. Try downloading some other rom and push it via adb.
Click to expand...
Click to collapse
Yup its 2.7. Should i wipe then try adb push without restoring? (ill have to wait and give it a go on my lunch break) and i have CM11 to install which i have been trying to push using adb but i either get protocol failure and the phone is restarting or it still says read-only file system. Do you think just wiping all except internal and doing a factory reset will help me get past the whole read only file system issue?
Slashkun said:
Yup its 2.7. Should i wipe then try adb push without restoring? (ill have to wait and give it a go on my lunch break) and i have CM11 to install which i have been trying to push using adb but i either get protocol failure and the phone is restarting or it still says read-only file system. Do you think just wiping all except internal and doing a factory reset will help me get past the whole read only file system issue?
Click to expand...
Click to collapse
lets say adb is in c:\adb
start, cmd (you run the cmd)
cd c:\adb
(copy your rom also somewhere with short path, let's say c:\adb\rom.zip)
adb push rom.zip /sdcard/rom.zip
or
adb push c:\adb\rom.zip /sdcard/rom.zip
adb sideload doesn't have to be enabled
bender_007 said:
lets say adb is in c:\adb
start, cmd (you run the cmd)
cd c:\adb
(copy your rom also somewhere with short path, let's say c:\adb\rom.zip)
adb push rom.zip /sdcard/rom.zip
or
adb push c:\adb\rom.zip /sdcard/rom.zip
adb sideload doesn't have to be enabled
Click to expand...
Click to collapse
Thanks for your continued assistance, however its still showing up as as a read only file system in cmd and thus it cannot copy. Do you have any other ideas? I have tried adb remount and it is still coming up with the read only error
The only thing i can think of is to use an microsdreader like meenova and put a rom on the microsd and put it in your phone but i dont know or your twrp supports otg.
Slashkun said:
Thanks for your continued assistance, however its still showing up as as a read only file system in cmd and thus it cannot copy. Do you have any other ideas? I have tried adb remount and it is still coming up with the read only error
Click to expand...
Click to collapse
Let me try to assist you when I get home.
bender_007 said:
Let me try to assist you when I get home.
Click to expand...
Click to collapse
Thanks so much for taking the time out to help me, this is way above my comfort zone
wulsic said:
The only thing i can think of is to use an microsdreader like meenova and put a rom on the microsd and put it in your phone but i dont know or your twrp supports otg.
Click to expand...
Click to collapse
I have an OTG cable and it is there as an option under TWRP and i tried putting the roms on my 32gb stick and plugged it into the phone using the OTG cable however when i clicked mount OTG it just stalled for a bit and the option was never ticked, also looking through file manager when the cable was connected i did not see anything or the blue light on my usb stick illuminate. If i was doing it wrong please let me know though
Slashkun said:
Thanks so much for taking the time out to help me, this is way above my comfort zone
I have an OTG cable and it is there as an option under TWRP and i tried putting the roms on my 32gb stick and plugged it into the phone using the OTG cable however when i clicked mount OTG it just stalled for a bit and the option was never ticked, also looking through file manager when the cable was connected i did not see anything or the blue light on my usb stick illuminate. If i was doing it wrong please let me know though
Click to expand...
Click to collapse
-p m
@usb - try formatting it through windows once again. I've also had some issues with my usb stick.
Just thought i would throw out and update to see if it helps you guys troubleshoot.
After doing an advanced wipe when i use the power off through TWRP it mentioned that i have no SU installed and asks me if i wish to install it. I click yes and it does something quickly then my phone restarts (so not sure if it worked or not) however every time i try and do and adb push to my device now it just comes up with protocol failure and restarts the phone. Just to note when i do a restore to the non-working backup i have when i try and turn it off using that it does not prompt that i do not have SU.
So i hope this helps in some way, nut sure if getting these protocol failure errors is better then the read only errors i was getting but the fact that it keeps restarting my phone does not seem promising when i do this.
Slashkun said:
Just thought i would throw out and update to see if it helps you guys troubleshoot.
After doing an advanced wipe when i use the power off through TWRP it mentioned that i have no SU installed and asks me if i wish to install it. I click yes and it does something quickly then my phone restarts (so not sure if it worked or not) however every time i try and do and adb push to my device now it just comes up with protocol failure and restarts the phone. Just to note when i do a restore to the non-working backup i have when i try and turn it off using that it does not prompt that i do not have SU.
So i hope this helps in some way, nut sure if getting these protocol failure errors is better then the read only errors i was getting but the fact that it keeps restarting my phone does not seem promising when i do this.
Click to expand...
Click to collapse
Well i guess you now have SU but the best thing to do is try to update the SU.
Try to Enable Usb debugging if it wasn't on yet. (I never had your error)
And also try to execute this when pushing a rom:
Code:
adb /kill-server
adb usb
adb push (romname) /sdcard
Or
adb push (romname) /storage/sdcard0
I don't know really about the last part anymore with adb pushing or these sdcard locations I said are right. The last time I used it was when i still had my phone :/
I hope this could fix your problem when you maybe accidently formatted your internal storage. If my sdcard locations aren't right could you correct me then? so people who also have this issue can fix it easily.
Thankyou
if you are out there @me2151 I could really use your help...
I have gone through all the steps multiple times and when I get to the part to get rid of the static on boot up, specifically when you get here:
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
**************
Once you are booted and have proceeded through the setup wizard, re-enable Android Debugging (ADB) if not already enabled.
Type:
Code:
adb reboot bootloader
6) Once inside bootloader, Type:
Code:
fastboot flash boot boot2.img
When it says finished, Type:
Code:
fastboot reboot
The device will boot back into system.
Click to expand...
Click to collapse
Once I reboot from this point I get the repeated phone app crash bug. I even tried the steps beyond this and reflashed SuperSU.zip, did the wipe, and reboot. Still get the phone app crash bug.
What am I missing?
Thanks in advance!
actschp1 said:
if you are out there @me2151 I could really use your help...
I have gone through all the steps multiple times and when I get to the part to get rid of the static on boot up, specifically when you get here:
Once I reboot from this point I get the repeated phone app crash bug. I even tried the steps beyond this and reflashed SuperSU.zip, did the wipe, and reboot. Still get the phone app crash bug.
What am I missing?
Thanks in advance!
Click to expand...
Click to collapse
I am going to assume you are on sprint. In which case you did not properly read the guide. You do not flash boot2 after installing the sprint rom. It specifically says for sprint users to stop right after you install the rom and supersu... Custom kernels will cause the phone crash.
actschp1 said:
if you are out there @me2151 I could really use your help...
I have gone through all the steps multiple times and when I get to the part to get rid of the static on boot up, specifically when you get here:
Once I reboot from this point I get the repeated phone app crash bug. I even tried the steps beyond this and reflashed SuperSU.zip, did the wipe, and reboot. Still get the phone app crash bug.
What am I missing?
Thanks in advance!
Click to expand...
Click to collapse
me2151 said:
I am going to assume you are on sprint. In which case you did not properly read the guide. You do not flash boot2 after installing the sprint rom. It specifically says for sprint users to stop right after you install the rom and supersu... Custom kernels will cause the phone crash.
Click to expand...
Click to collapse
Ok, stopped there. But on your guide it says there will be static on reboots if I stop at that point. I was thinking that I was suppose too follow the remaining steps to get rid of the static boot. Since that is not the case, I take it there is no way to eliminate the static on boot up?
actschp1 said:
Ok, stopped there. But on your guide it says there will be static on reboots if I stop at that point. I was thinking that I was suppose too follow the remaining steps to get rid of the static boot. Since that is not the case, I take it there is no way to eliminate the static on boot up?
Click to expand...
Click to collapse
Not as of now. Just continue to use the proximity sensor fix until further notice.
Mind Absent// said:
Not as of now. Just continue to use the proximity sensor fix until further notice.
Click to expand...
Click to collapse
Ok, thanks for the info @Mind Absent//
@me2151, and all those who worked on this, are freakin rockstars to get us to this point. Static is nothing since it's such an easy fix.
actschp1 said:
Ok, thanks for the info @Mind Absent// @me2151, and all those who worked on this, are freakin rockstars to get us to this point. Static is nothing since it's such an easy fix.
Click to expand...
Click to collapse
Lol, I'm just the messenger. Thank @me2151 and his team for all their hard work and perseverance in something that seemed so impossible only 2 months ago.