So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.
Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent
ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?
ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.
Related
if this is the wrong place for this SORRY IN ADVANCE
ok so after rooting my shift i followed all the steps got the recovery on there and downloaded a ROM and wiped everything and when the rom flashed it said error 7 instalation aborted so i hit reboot system now just to see what would happen because i did wipe everything so i was expecting to be stuck at the boot img..no problem was just playing around but the thing actually booted in a rom that looks 100% stock....what happened
even tho the ROM looks 100% stock it is def not i have adfree and esfile explorer added to app drawer now if its gonna flash the rom anyways why does cw 2.5.1 tell me its a no go with a stauts 7 i have even formatted my card to wipe it 100% and the same thing happens>?
when you "wipe" you're not wiping the rom. The data, cache etc yes. Only a rom install overwrites a prior rom. unless you format the phone.
RyteSyde said:
when you "wipe" you're not wiping the rom. The data, cache etc yes. Only a rom install overwrites a prior rom. unless you format the phone.
Click to expand...
Click to collapse
yeah it must have just been an issue with the rom i was flashing because i flashed another one no problem thanks for that bit of info though
I had no problem flash nfinites stock rom...must have been something you did...not so much the rom...
Sent from my PG06100 using XDA App
JKILO said:
I had no problem flash nfinites stock rom...must have been something you did...not so much the rom...
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
People that flashed the base steel posted had similiar issues. E.G. if you were on cm6 and wiped, then flashed the base, you'd boot into a fresh cm6. The partitions were setup wrong, I believe.
Sent from my Speedy Shift.
smoothtaste said:
People that flashed the base steel posted had similiar issues. E.G. if you were on cm6 and wiped, then flashed the base, you'd boot into a fresh cm6. The partitions were setup wrong, I believe.
Sent from my Speedy Shift.
Click to expand...
Click to collapse
Ok my fault...never took notice..thanks
Sent from my PG06100 using XDA App
I just rooted for the first time yesterday so I'm fairly new to all this... is it common practice to wipe cahce/dalvik prior to flashing any ROM?
I've gone back and forth from the stock ROM to another custom Sense ROM without wiping and no issues. Is it only advised if something goes wrong? Also, is there an issue with just going into recovery and wiping cache when NOT flashing a new ROM (just rebooting to the same one I'm using)? Thanks for the help.
HolyShift said:
I just rooted for the first time yesterday so I'm fairly new to all this... is it common practice to wipe cahce/dalvik prior to flashing any ROM?
I've gone back and forth from the stock ROM to another custom Sense ROM without wiping and no issues. Is it only advised if something goes wrong? Also, is there an issue with just going into recovery and wiping cache when NOT flashing a new ROM (just rebooting to the same one I'm using)? Thanks for the help.
Click to expand...
Click to collapse
Its good practice to always wipe. You may get by without it a few flashes. But eventually you'll be haunted by force closes, boot loops, etc.
Personally when I flash a new rom after the data, cache and dalvik wipes I format my boot, system, data and cache partitions manually via the mounts menu.
From experience, to truly see changes in rom updates or properly enjoy an entirely different one, this eliminates most problems before they ever manifest.
Sent from my Speedy Shift.
Hello guys.
I would really appreciate an answer to a question I have.
I installed leedroid 3.0.2 and I have the same apps and settings as before.
I think I haven't done a good wipe..
I rebooted to recovery from cwm and used the wipe before I installed the new Rom. (i was using the revolution 3.5 before)
After I installed the new Rom, when I booted on, all apps and settings were there.
Shouldn't the wipe thing clean everything and leave the phone "empty"?
Or, (most obvious) did I do something wrong and should do it again? Cause there is a little thing with the market that closes the process when I click on new released apps.
Thank you in advance guys.
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
GeorgeKps said:
Hello guys.
I would really appreciate an answer to a question I have.
I installed leedroid 3.0.2 and I have the same apps and settings as before.
I think I haven't done a good wipe..
I rebooted to recovery from cwm and used the wipe before I installed the new Rom. (i was using the revolution 3.5 before)
After I installed the new Rom, when I booted on, all apps and settings were there.
Shouldn't the wipe thing clean everything and leave the phone "empty"?
Or, (most obvious) did I do something wrong and should do it again? Cause there is a little thing with the market that closes the process when I click on new released apps.
Thank you in advance guys.
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
Click to expand...
Click to collapse
Are you wiping data and cache in recovery?
"wipe data/factory reset"
It will then say:
Code:
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
Then:
"wipe cache partition"
It will say:
Code:
-- Wiping cache...
Formatting /cache...
Cache wipe complete
(second option is overkill)
Have you still got the setting to backup to Google servers ticked? Or any other app that you have backed things up with?
Whilst the last option wouldn't be instant (they would download again and take a good 5 minutes to appear).
And yes, you will probably experience issues if this is due to a missed wipe.
So, I will need to do a factory reset first, then do a cache wipe and then install the Rom?
(i don't remember doing all these for the revo Rom..)
Do I need to do these without rebooting the phone until everything is done?
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
GeorgeKps said:
So, I will need to do a factory reset first, then do a cache wipe and then install the Rom?
(i don't remember doing all these for the revo Rom..)
Do I need to do these without rebooting the phone until everything is done?
Click to expand...
Click to collapse
Yes, you should always do the "wipe data/factory reset" before installing any new ROMs or if the dev has advised it, also between major update revisions.
You don't need to reboot. If using recovery to install the ROM just do the wipes then flash the ROM using menu.
Awesome. Thanks for the help.
Will try it now and I hope everything goes well. Hope I won't get stuck since am not in front of my pc.
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
Well, I did it again. Everything wiped out, started as new.
But still, new apps in market and battery history in spare parts give me a process termination...
Oh well, I guess that Lee will release an update.
Oh, something else I would like to ask. There is a new kernel for the Rom. Do I flash it the same way I flash everything? Through recovery?
Thanks again guys
Cheers !!!
Sent from my LeeDroid 3.0.2 Enhanced Desire HD
I use Leedroid and don't have this problem. Today I have installed from scratch and gone back and forth between ROM's. i turned off all the processes that backup and restore apps and I get a blank fresh install.
I have to ask, the last time you installed Leedroid, did you use the downloaded one or a copy from your sdcard? is it possible you are restoring a copy rather than flashing a fresh copy?
And you don't have any apps that have backed up your apps such as Titanium? And you have turned off Google Backup and restore feature?
The thing is, it is handy not to lose data but we need to make sure your wipe is being done. Did you see the same messages in Recovery as I showed above?
gosh, it is sooooooooooooo weird...
i did it all again. factory reset, delete cache, installed the 3.0.3 version (which was released today).
everything seemed to go smooth. still, i went to market and clicking on the newly released apps list i get an error which is "com.android.vewnding" has been shut blah blah blah. and the same happens to spare parts. when i click battery history ""com.android.spare_parts" shuts down.
do you guys think it has to do with the kernel? should i flash lee's kernel (i couldn't find how to. i mean, shall i do it from the cwm recovery?)
i guess that the radio has nothing to do with all these, does it?...
thank you guys once again for your help
Cheers !!!
GeorgeKps said:
gosh, it is sooooooooooooo weird...
i did it all again. factory reset, delete cache, installed the 3.0.3 version (which was released today).
everything seemed to go smooth. still, i went to market and clicking on the newly released apps list i get an error which is "com.android.vewnding" has been shut blah blah blah. and the same happens to spare parts. when i click battery history ""com.android.spare_parts" shuts down.
do you guys think it has to do with the kernel? should i flash lee's kernel (i couldn't find how to. i mean, shall i do it from the cwm recovery?)
i guess that the radio has nothing to do with all these, does it?...
thank you guys once again for your help
Cheers !!!
Click to expand...
Click to collapse
You have tried fix permissions in ROM Manager, yes?
eeeeeeeeeerm.... you got me. that is something i totally forgot to do :-(((
gosh.. i flashed the radio, sweet. tried to flash a kernel using jkoljo's tool and it stayed on the white screen (and of course cold sweat was all over the place )
but i flashed the rom again after clearing cache and the likes and (thank god) i'm in.
but the most weird thing is that, after all these, the kernel is flashed :-S
i checked in the phone info and the kernel is there..
anyway, am gonna do the fix permissions thingy and reflash once more. if it stays the same way, i'll have to live with it. it's late here in greece.
thanks again for your help guys, i really appreciate it )))
Cheers !!!
i did it all again but nothing happened.
did the permissions, rebooted to recovery, factory reset, cache wipe, install new rom and nothing.
i have to tell you guys though.. the problem with the market started when i was on the revolution rom. and it started just like that. one day everything was fine, next, bam. it didn't budge.
do you think there might be something wrong with the phone itself? (probably not and i'm paranoid)
other than that, everything works nice.
oh, and some other thing. there is this "full wipe 1.3" zip i had put in my SD card but never really used it.
should i use it this time?
this app should clean everything in the cache but not my files, right?
Cheers !!!
YouTube clip of how to manually full wipe everything.
http://www.youtube.com/watch?v=fCwr6Ru0yko
When using this method I've never had a problem.
Sent from my HTC Desire HD using XDA App
I did the wipe as shown in the video. The problem remains the same. New market apps list gives an error followed by a restart of it and spare parts battery history does the same (without the restart though)
I don't know, I'm thinking of trying a different Rom even though I like the one Lee released.
(could all this mean that I have a problem with the phone?.......)
Anyway, thank you guys for spending time helping me.
Cheers !!!
Hello All,
I am hoping the XDA community can help me out.
My current situation is that I am rooted, runnig Madhi 4.4.2 rom. I also have TWRP installed, with backup for stock rooted rom, and a backup for
my current Madhi Rom. Here lies my problem. I can't flash any other rom, nor can I flash my stock backup rom.
When I try to flash a different rom I get bootloops causing it to constantly restart, which is the same thing that happens when i try to flash my stock
backup. Can someone be kind enough to tell me what I am doing wrong (before i was able to restore my backup to stock), and what do i need to
do to be able to change out my rom. Hopefully there is a way to do so without having to bring my phone completely back to stock, then rerooting.
I've searched the threads but i wasn't able to find the answer.
Thanks in advance for your help guys.
JD
jdizzle316 said:
Hello All,
I am hoping the XDA community can help me out.
My current situation is that I am rooted, runnig Madhi 4.4.2 rom. I also have TWRP installed, with backup for stock rooted rom, and a backup for
my current Madhi Rom. Here lies my problem. I can't flash any other rom, nor can I flash my stock backup rom.
When I try to flash a different rom I get bootloops causing it to constantly restart, which is the same thing that happens when i try to flash my stock
backup. Can someone be kind enough to tell me what I am doing wrong (before i was able to restore my backup to stock), and what do i need to
do to be able to change out my rom. Hopefully there is a way to do so without having to bring my phone completely back to stock, then rerooting.
I've searched the threads but i wasn't able to find the answer.
Thanks in advance for your help guys.
JD
Click to expand...
Click to collapse
What version of TWRP are you running and how are you wiping? Make sure you go into advanced and wipe cache, dalvik, data AND system.
Do this 3 times! Because sometimes it doesn't work. Flash your rom then wipe cache and dalvik and restart.
scottdanpor said:
What version of TWRP are you running and how are you wiping? Make sure you go into advanced and wipe cache, dalvik, data AND system.
Do this 3 times! Because sometimes it doesn't work. Flash your rom then wipe cache and dalvik and restart.
Click to expand...
Click to collapse
Thanks for the tip. I am running 2.6.3.3 TWRP.
I normally do the full wipe, but i took your advice and went into advanced wipe and wiped dalvik, cache, system & data but unfortunately still the same result.
do you have any idea of what boggered up my phone? for right now, im stuck on Mahi Rom. I can restore back to Mahi Rom, and flash Mahi Rom, but that's the extent of it.
I do recall that when I originally flashed Mahi Rom, i had to flash a patch for the Sprint version of the G2. Do you think that has something to do with my problems?
i didn't have this problem before...just kinda baffled that now its giving me issues....
Thanks for your time, much appreciated. Hope someone can help me get to the bottom of this
JD
jdizzle316 said:
Thanks for the tip. I am running 2.6.3.3 TWRP.
I normally do the full wipe, but i took your advice and went into advanced wipe and wiped dalvik, cache, system & data but unfortunately still the same result.
do you have any idea of what boggered up my phone? for right now, im stuck on Mahi Rom. I can restore back to Mahi Rom, and flash Mahi Rom, but that's the extent of it.
I do recall that when I originally flashed Mahi Rom, i had to flash a patch for the Sprint version of the G2. Do you think that has something to do with my problems?
i didn't have this problem before...just kinda baffled that now its giving me issues....
Thanks for your time, much appreciated. Hope someone can help me get to the bottom of this
JD
Click to expand...
Click to collapse
I'm baffled as well, I would say it's time for a .tot restore. The rooting doesn't take long really, I think you'll spend more time trying to troubleshoot than it takes to wipe and restore your apps with TBU.
Are you by chance using the zva radio?
Sent from my LS980 4G using Tapatalk
scottdanpor said:
I'm baffled as well, I would say it's time for a .tot restore. The rooting doesn't take long really, I think you'll spend more time trying to troubleshoot than it takes to wipe and restore your apps with TBU.
Click to expand...
Click to collapse
Thanks for taking the time out to help me out. I'm afraid you might be right. It's just the the files for the .tot restore are huge! One file was over 2.1 gb, which sucks for me cause my internet is really slow. funny thing is i was dl'ing that file took like 5 hours, and when it got to 2gb downloaded, the site froze and i wasn't able to pause/resume my download. it was very frustrating.
Dshook1979 said:
Are you by chance using the zva radio?
Sent from my LS980 4G using Tapatalk
Click to expand...
Click to collapse
I don't think i ever updated my radio. is this something i should do in order to flash or restore?
jdizzle316 said:
Thanks for taking the time out to help me out. I'm afraid you might be right. It's just the the files for the .tot restore are huge! One file was over 2.1 gb, which sucks for me cause my internet is really slow. funny thing is i was dl'ing that file took like 5 hours, and when it got to 2gb downloaded, the site froze and i wasn't able to pause/resume my download. it was very frustrating.
Click to expand...
Click to collapse
Most roms are around 1.5gb. If you are getting disconnects it could also be causing what you see with the other roms you're flashing. Unless they are the same ones that you flashed successfully before of course.
Either way having a .tot restore file backup up on your PC is really handy to have.
scottdanpor said:
Most roms are around 1.5gb. If you are getting disconnects it could also be causing what you see with the other roms you're flashing. Unless they are the same ones that you flashed successfully before of course.
Either way having a .tot restore file backup up on your PC is really handy to have.
Click to expand...
Click to collapse
Thank you again...thats what im going to do tonight after work.
Last night my phone wanted to update to 4.4.4 because it's been wanting to for a while, but I know it wouldn't work because my phone is rooted. It had tried this at least 3 times before and everything was fine; download update, tries to install, fails, boots right back up. I wanted to get rid of the Update notification in the top bar, so I just ran it again thinking it'd be okay. Well, this time it bricked my phone, leaving me at a neverending loop at the boot animation. I first tried to wipe the cache and dalvik cache, which did nothing. Then I tried a factory restore, which also did nothing. Then I reinstalled the stock 4.4.3 rom I had been using, which did nothing. Then I wiped the SD card completely and reinstalled a stock 4.4.4 rom through sideload, which has done nothing. My phone just sits at the boot animation and taunts me. Worse yet, I have a 16-hour drive tomorrow and my phone was going to be the majority of my sanity during that time.
What should I do?? Is there anything I can do? Normally I would just contact Google to get a replacement (I've done this before when the 4.2 update was causing a lot of bricks,I think it was 4.2 anyway, I forgot) but I'd like to have a working phone for my 16 hour trip..... if possible. Any help would be greatly appreciated! Thank you.
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
CCody said:
Well, I never had heard of any devices that still stuck in the bootanimation after flashing the factory image. There is something really wrong.
Did you already tried flashing a custom rom? Can you boot into recovery?
Click to expand...
Click to collapse
I had a Vanir 4.4.3 rom on my phone that I tried to flash as well, but for some reason it went right into "Optimizing Apps" after the first boot, something I hadn't seen before. Then it got stuck at "Starting Apps...", then after a restart, it too was stuck at the boot animation.
I can boot into recovery luckily, but that's all I can do. I have CWMR v6.0.3.5. I've tried just about everything I can think of. [edit] I was able to contact Google for some live chat support and am now #2 in the queue. Hopefully they can either help me or get a replacement going. Either way, I'd still love any help you guys can give me, I'd really like to get it fixed rather than waiting for a replacement.
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
CCody said:
Okay, try this: Wipe everything via recovery and with everything i mean really everything! Cache, dalvik, storage, your whole system. There must be nothing left on your phone. Then flash a rom of your choice. Wipe cache and dalvik afterwards and see if it works
Click to expand...
Click to collapse
I've done that already, Factory Reset + wipe cache + wipe dalvik cache + format system/data/cache/sdcard/data/media. The phone was completely bare and that's when I sideloaded the stock 4.4.4 rom (otherwise it's stuck at the Google boot screen). I'll try it again, though.
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
RawrNate said:
Okay right now I'm using the Nexus Toolkit to flash the stock 4.4.4 .tgz image directly from google and unroot my phone (checking the option that the phone is Soft-bricked/Bootloop.
....Okay that finished and I'm still stuck at the boot animation and now I don't have CWMR. ****. [EDIT] But I can still boot into a custom recovery through the toolkit, which is good.
Click to expand...
Click to collapse
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
CCody said:
Damn, I really am stumped right now. That's really strange. Normally everything should be fine after a factory reset...
I've search several threads with bootloop problems, but none of them have this persistent bootloop. I believe you have damage your storage somehow, so that the system can't read the files and boot up properly. Maybe because of this 4.4.4 OTA update. Man, that's kinda sucks right now...
Click to expand...
Click to collapse
Yeah haha, it's really really strange. I appreciate you trying to help me, though! Lucky for me I'm getting a "One-time exception replacement" since my warranty is expired but they must be super stumped with the issue as well xD
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
CCody said:
I forgot something! Did you also flashed the 4.4.4 binaries?
https://developers.google.com/android/nexus/drivers#makoktu84p
I also read somewhere, that the LG Fashtool may help.
Try this out!
Click to expand...
Click to collapse
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Wait, how do I flash the binaries since they're .tgz files?
RawrNate said:
Hm, I didn't think I'd need to with the factory image, but I'll try that. I tried the 4.4.3 factory image as well but that didn't work either. I also can't find anything about the LG Flashtool that's Nexus 4 specific, but I'll try to look more into it.
Click to expand...
Click to collapse
This is really strange man. Flashing stock ROM is the last resort but even that seems to be failing for you.
Have you tried downloading the stockRom again (just to make sure it isn't corrupted). Also, maybe you can try using TWRP instead of CWM this time.
Good luck.
RawrNate said:
Wait, how do I flash the binaries since they're .tgz files?
Click to expand...
Click to collapse
No need to flash them, since you are on a factory image, sry.
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
RawrNate said:
Woah now, I've made progress! Maybe.... Anyway, in TWRP, I "fixed permissions" and mounted "system" but now I'm at the "Android is Upgrading, Optimizing Apps - Starting Apps" screen again (it only had to optimize 23 apps?). I was at this issue before when I was flashing roms last night trying to fix it, but going back to here is better than not getting it to boot at all. What else should I try next?
Note: I'm on the 4.4.4 factory image now and TWRP is just temporary through the Nexus Root Toolkit.
Click to expand...
Click to collapse
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
CCody said:
And? Did it boot up or just stuck in 'optimizing apps'? I would suggest to try another android version, like 4.3 or 4.4.2 at least.
Click to expand...
Click to collapse
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
RawrNate said:
30 minutes later and it's still at "Starting apps..."
I tried factory images of 4.4.3 and 4.3, still nothing.
Click to expand...
Click to collapse
Jesus!
What about custom ROM? Cyanogenmod maybe? Make sure to downlaod the M7-Release.
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
RawrNate said:
Hm, alright, I'll give that a shot.
On a side note, is there a way to lock the bootloader again while in either recovery or bootloader? I fear that if it's unlocked, I won't get the $250 refund for the replacement.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=tZbvuikfnks
CCody said:
https://www.youtube.com/watch?v=tZbvuikfnks
Click to expand...
Click to collapse
Oh good that was easier than I thought xD
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Info
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Which partitions are you backing up when creating the nandroid with TWRP?
Heisenberg said:
Which partitions are you backing up when creating the nandroid with TWRP?
Click to expand...
Click to collapse
System, data, boot - Installing the kernel made no difference, the device still corrupted on reboot. and then sometimes at least twice it has soft-bricked
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Already tried it mate, a number of times. no joy.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
XxMORPHEOUSxX said:
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
Click to expand...
Click to collapse
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Xtra-arrow said:
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Click to expand...
Click to collapse
Maybe this will be helpful. I think you have the red level warning like this user. Seems like the exact same situation.
http://forum.xda-developers.com/showthread.php?p=64403982
Turns out it isn't bootlooping. Its taking at least 3 minutes to turn on. It looks like bootlooping. BUt if finally loaded. After doing my uninstalling of aomw system apps. Its rebooted and keeps optimising apps. 2-4 then restarts and does same
Info
Heisenberg said:
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Click to expand...
Click to collapse
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
No it isn't necessary to wipe the userdata partition. No modifications are stored in the userdata partition. It would only be necessary to wipe system, data, cache, and dalvik cache. And probably flash the vendor partition too. Not userdata though.
I had a similar problem when I botched a SU flash, same warning then it would take forever to boot, then the rom would degrade over the next several minutes. I know its not fun to start over, but it was the only thing that cleared all the problems. I didn't want to take more time finding another solution when going back to stock is so simple with this device. Follow the instructions in step #11 of Heisenberg's guide (great guide, I link it to friends a lot). Then start again, I know, not what you wanted to hear. Hope this helps!
I am also in agreement with Heisenberg in regards to the userdata partition.
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Info
Xtra-arrow said:
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Click to expand...
Click to collapse
If you are sure about reason Forget ur Backups.
you should completely install Stock Kernel, Rom, Boot.img >> Back to Stock
But If I remember correctly u did this before...
I just have to say Retry Also Install and use Nexus Root Toolkit
:good:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Xtra-arrow said:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Click to expand...
Click to collapse
Can I ask what gapps are you using? Are you using your google account to recover your apps, or are starting fresh each time?
Sent from my Nexus 6P using Tapatalk
Thanks for your reply. I've actually now narrowed itnright down to a few apps, maybe gapps. Sound recorder, voice recorder app and the google app. Either one or more of these cause my optimising apps bootloop.