Please if someone can take the time to help me save a lot of time.
So I had to restore my Nexus 6 back to stock from CM12 to unlock the phone so I could start using Project Fi. So I went back set it up and was ready to restore back to cm12. Well every time I try to go back to one of my updates it runs for maybe a min and then the phone restarts and then just stays on start up screen without starting up.
this has nothing to do with the unlocking of the phone because 2 months ago when I needed to restore from cm12 it did the same thing!
So why cant I restore using twarp on my device and what do I have to do to get back my restore.
also when I try to just reload cm12 it fails .
PLEASE HELP ME SOMEONE! LOL
CM is your first problem. LOL All that aside. Usually when it stops on startup screen the kernel is borked. Try fastbooting/flashing a compatible kernel.
Try wipe cache and dalvik from recovery. If it still doesn't boot, wipe data, then restore apps using titanium
Can you guys please look at clip I made of the issue. Thanks so much!
https://youtu.be/3C8LtPu9LsA
<iframe width="420" height="315" src="https://www.youtube.com/embed/3C8LtPu9LsA" frameborder="0" allowfullscreen></iframe>
No need. Follow our advice
enzosly said:
Can you guys please look at clip I made of the issue. Thanks so much!
https://youtu.be/3C8LtPu9LsA
<iframe width="420" height="315" src="https://www.youtube.com/embed/3C8LtPu9LsA" frameborder="0" allowfullscreen></iframe>
Click to expand...
Click to collapse
To start I would actually wipe. Dalvik and cache is not a wipe. This only affects apps saved in ram.. Wipe system. Your flashing over old system and data. It is different flashing images than it is flashing restores. Can have files that are not overwritten. Basically a full dirty flash. Can't go stock and then dirty flash rom over the top. Especially CM. Too much doesn't match. Your flashing different bases over the top of each other. This is why people need permission fixes. The UID's don't match between the different bases. Have never used fix permissions unless testing and then shows us need to fully wipe.
prdog1 said:
To start I would actually wipe. Dalvik and cache is not a wipe. This only affects apps saved in ram.. Wipe system. Your flashing over old system and data. It is different flashing images than it is flashing restores. Can have files that are not overwritten. Basically a full dirty flash. Can't go stock and then dirty flash rom over the top. Especially CM. Too much doesn't match. Your flashing different bases over the top of each other. This is why people need permission fixes. The UID's don't match between the different bases. Have never used fix permissions unless testing and then shows us need to fully wipe.
Click to expand...
Click to collapse
ok so do a full wipe is what your saying then? Ill give it a try
enzosly said:
ok so do a full wipe is what your saying then? Ill give it a try
Click to expand...
Click to collapse
Yes. Also make sure boot is checked when make a backup. If restore doesn't contain kernel CM won't boot with stock kernel.
prdog1 said:
Yes. Also make sure boot is checked when make a backup. If restore doesn't contain kernel CM won't boot with stock kernel.
Click to expand...
Click to collapse
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
enzosly said:
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
Click to expand...
Click to collapse
Backup may be bad. Wipe everything and flash a full image/rom. Stopping on the splash usually means corrupted kernel. Rom not booting. If get to boot animation it is rom related. Need to start fresh. Google saves your apps so it no big deal. Rather have clean working rom than worry about apps and resetup.
enzosly said:
Ok so I did a full wipe and still same thing. I also went into fixing permissions and nothing.
what should I do next I guess? again thank you for taking the time
Click to expand...
Click to collapse
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
danarama said:
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
Click to expand...
Click to collapse
I agree if have to fix permissions rom is borked. Still looks like corrupted backup. Wipe all and fastboot stock or flash clean rom.
danarama said:
NEVER fix permissions.
Download the rom and flash it. Then use titanium to restore apps.extracted from.your nandroid.backup, if it can.
Click to expand...
Click to collapse
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
simms22 said:
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
Click to expand...
Click to collapse
It fixes mismatched UIDs which means you have a corrupt install. LOL
simms22 said:
fix_permissions works, but not via recovery. i use stericsons fix_permissions app. it goes through and fixes permissions, per each app, when you are fully booted.
Click to expand...
Click to collapse
Thing is they can't know what permissions everything is supposed to have, so its guess work and can lead to more problems l. Besides, permissions should never need fixing anyway
prdog1 said:
It fixes mismatched UIDs which means you have a corrupt install. LOL
Click to expand...
Click to collapse
whatever.. last time i installed anything was when m came out. honestly, ill use that app maybe twice a year, but it does work.
---------- Post added at 03:10 PM ---------- Previous post was at 03:08 PM ----------
danarama said:
Thing is they can't know what permissions everything is supposed to have, so its guess work and can lead to more problems l. Besides, permissions should never need fixing anyway
Click to expand...
Click to collapse
na, it doesnt ever need fixin', its just something ill do every once in a while. kind of a habit leftover from the older android days.
simms22 said:
whatever.. last time i installed anything was when m came out. honestly, ill use that app maybe twice a year, but it does work.
Click to expand...
Click to collapse
Just saying after years as a tester and thousands of builds. Was a big thing when they were porting roms to a different device. UIDs were broke all over the place. See the same thing if dirty flash different bases like Lolli over KitKat or a complete base change as an example ( L to M). Don't see mismatched UID's on updates made on same base.
prdog1 said:
Just saying after years as a tester and thousands of builds. Was a big thing when they were porting roms to a different device. UIDs were broke all over the place. See the same thing if dirty flash different bases like Lolli over KitKat or a complete base change as an example ( L to M). Don't see mismatched UID's on updates made on same base.
Click to expand...
Click to collapse
im very known as a dirty flasher btw :angel:
(and i did dirty flash m over terminus)
simms22 said:
im very known as a dirty flasher btw :angel:
(and i did dirty flash m over terminus)
Click to expand...
Click to collapse
Some have the luck. Apparently this poster don't.
prdog1 said:
Some have the luck. Apparently this poster don't.
Click to expand...
Click to collapse
its not luck, its all about doing it properly
Related
Stock Rooted OTA 4.08.605.19 710RD Rom
Stock rooted ota 4.08.605.19 710RD rom. It is rooted, zip aligned, has busybox and comes in odexed or deodexed versions. Other than that it is untouched. Enjoy
[standard flashing disclaimer here]
Do a full wipe (boot, system, data, datadata, cache, android secure) except for sdcard and emmc, then flash like any other rom.
Stock rooted ota 4.08.605.19 rom may be able to be flashed over Stock rooted ota 4.08.605.15 rom, but is untested. If you flash over and have issues, do a full wipe and fresh install.
DOWNLOAD ODEXED - MD5 - Mirror
DOWNLOAD DEODEXED - MD5 - Mirror
_
2-13-2013 - Fixed TWRP flashing issues.
3-13-2013 - Fixed Superuser issues.
Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.
ToyTank said:
Sweet! Thank your sir.
Been waiting for this- One question I forget on the Dinc can you delete system apps on the phone?
I just activated my dinc again on pagepluscellular($12) I have to say for it's age the little guy holds up well. Looking forward to more roms and hopefully no more 2am reboot issue.
Click to expand...
Click to collapse
Just grab a root file explorer.
Sent from my Nexus 7 using Tapatalk 2
Osiris19 said:
Just grab a root file explorer.
Click to expand...
Click to collapse
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.
ToyTank said:
Thank you I forgot dinc has that level of system access just with root. IIRC titanium bu can also.
Click to expand...
Click to collapse
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?
IceDragon59 said:
I pulled out my old Incredible to see if I could breathe some new life into it and updated it to TWRP 2.4.1.0 and made a NANdroid backup of my old ROM. Went to go install it and get the Status 2 error, so I put in a newer update-binary. Not a big deal. I go to flash it again, and I get the Status 7 error, meaning I need to update to a newer version of my recovery. Not possible! So I re-flashed recovery and tried again. No dice. I can still restore my backup, so it's still alive right now. I'm curious to know if anyone else is experiencing this. Does anyone have any ideas?
Click to expand...
Click to collapse
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.
cmlusco said:
Let me do some testing. I made it twrp compatible but never tested with twrp only cwm. I may have messed something up.
EDIT: FIXED!! Thanks for bringing it to my attention. I haven't gotten much feedback so far. Just redownload and flash.
Click to expand...
Click to collapse
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.
IceDragon59 said:
Your zip works now. What was the problem?
Also, I've always been able to edit ROM zips and delete and add apks without any issue, but I can't now with this one. It keeps giving me the status 7 error about 80% through the install when all I do is delete some Verizon bloat from the zip file. Your zip is fine, it's just when I modify it that it's giving me a problem. I'm not using the MD5 file, so it shouldn't affect anything. Also, I don't think it should let me get 80% done with the install before it breaks only because of some deleted files.
Click to expand...
Click to collapse
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.
cmlusco said:
Had to update the update-binary, and edit the mount commands in the updater-script.
Deleteing apps from /system/app in the rom zip should not affect the zip in any way. Are you just deleting them from within 7zip, or are you unziping, deleting, and then rezipping it?
Status 7 usually reffers to an error in the updater-script. Since it stoped about 80% thru, about 80% thru the updater-script is where the issue is.
Click to expand...
Click to collapse
Deleting them in WinZip. That's how I've always successfully done it before.
IceDragon59 said:
Deleting them in WinZip. That's how I've always successfully done it before.
Click to expand...
Click to collapse
I will try it and see if it does the same for me.
cmlusco said:
I will try it and see if it does the same for me.
Click to expand...
Click to collapse
Any luck?
IceDragon59 said:
Any luck?
Click to expand...
Click to collapse
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.
cmlusco said:
Sorry for the long wait. Yes i can remove system apps from the zip using 7zip without issues. Make sure you also delete the apks odex file too if using the odexed rom.
Click to expand...
Click to collapse
Thanks so much =), honestly I am surprised updates are still being released. I really need to get to a Verizon store and snag the 4G version but I've been traveling a lot so my Blackberry has been getting a workout thanks to the international SIM support. Regardless I still use my Dinc for Google Auth (2-pass auth FTW!) and other activities everywhere (in network or not).
Fixed issues with superuser. For those who have already downloaded reflash superuser http://dinc.does-it.net/Superuser/SuperUser_3.1.1.zip thru recovery.
Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.
leo72793 said:
Trying to install. Unlocked CWM 5.0.2.0 Error 7. Bar goes full the over the full and fails.
Click to expand...
Click to collapse
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.
cmlusco said:
Did you do a full wipe or a flash over. Was there a line before the status 7, what did it say? Symlink failed, expecting # arguments, unexpected? I will have a look at it, the last test i did was with twrp.
Click to expand...
Click to collapse
having pertition error :/
leo72793 said:
having pertition error :/
Click to expand...
Click to collapse
What kind of partition error?
I tested both cwm and twrp with both a flashover from stock rom 605.15 and a clean install and all worked just fine. Did you check the md5? Try redownloading.
Just got my INC back from my little sister after she upgraded and i'm excited to have this as my backup! Thanks for uploading this for everyone!
i wanted to root my xperia T but unfortunately DooMLoRD's guide doesn't work for me http://forum.xda-developers.com/showthread.php?t=2327472, i tried it out but it didn't do anything after getting daemon started.
i got the phone with JB 4.3 already so i thought that might be the reason, the build is 9.2.A.0.295 so i want to ask how to root it
TowelRoot has been confirmed to work for the T on 4.3 firmware, see topic in the General section
Sent from my LT30p using XDA Free mobile app
Mad Marty said:
TowelRoot has been confirmed to work for the T on 4.3 firmware, see topic in the General section
Sent from my LT30p using XDA Free mobile app
Click to expand...
Click to collapse
thank you, i'll do that immediately
unexpected problem
the root really worked and i was excited for about half a day but now i noticed that i can't connect to google play, nor my account sync works, what should i do?
you could flash a recovery and then flash gapps?
matt4321 said:
you could flash a recovery and then flash gapps?
Click to expand...
Click to collapse
i don't know, with i guide i should be able to but i've never done that, i only rooted the device i didn't flash any rom
i read somewhere on the forums that i can solve it by deleting etc/hosts but it tells me i don't have enough permissions to do so
dakuhonoo said:
i don't know, with i guide i should be able to but i've never done that, i only rooted the device i didn't flash any rom
i read somewhere on the forums that i can solve it by deleting etc/hosts but it tells me i don't have enough permissions to do so
Click to expand...
Click to collapse
have a look at this for a recovery: http://forum.xda-developers.com/showthread.php?t=2657190
being on stock is fine,
then GApps have a look here: http://www.androidfilehost.com/?w=files&flid=14705
matt4321 said:
have a look at this for a recovery: http://forum.xda-developers.com/showthread.php?t=2657190
being on stock is fine,
then GApps have a look here: http://www.androidfilehost.com/?w=files&flid=14705
Click to expand...
Click to collapse
i'm going to have to do that, i managed to delete the hosts file with root browser but it should have made a new one and it didn't, it also didn't solve the problem .. i'm trying this recovery now
ok i flashed it, probably, now what?
dakuhonoo said:
i'm going to have to do that, i managed to delete the hosts file with root browser but it should have made a new one and it didn't, it also didn't solve the problem .. i'm trying this recovery now
ok i flashed it, probably, now what?
Click to expand...
Click to collapse
You need to reboot into the recovery and flash the GApps (Google Apps) which should have all the sync and play store files to work
matt4321 said:
You need to reboot into the recovery and flash the GApps (Google Apps) which should have all the sync and play store files to work
Click to expand...
Click to collapse
i booted into recovery with quickboot and installed google core apps from sd card and wanted to reboot but it's telling me that "ROM may flash stock recovery on boot" choices : No | Yes - Disable recovery flash | No
what should i do?
dakuhonoo said:
i booted into recovery with quickboot and installed google core apps from sd card and wanted to reboot but it's telling me that "ROM may flash stock recovery on boot" choices : No | Yes - Disable recovery flash | No
what should i do?
Click to expand...
Click to collapse
'disable recovery flash'
Though it shouldn't change anything since this is a LB recovery and done in a completely different way
matt4321 said:
'disable recovery flash'
Though it shouldn't change anything since this is a LB recovery and done in a completely different way
Click to expand...
Click to collapse
funny, i'm so stressed out i messed up and chose No instead of Yes, thank you for you support so far
and it booted up and i'm still getting "Server error" on play store
do you think flashing the stock android over the mess i made would help? or factory reset?
dakuhonoo said:
funny, i'm so stressed out i messed up and chose No instead of Yes, thank you for you support so far
and it booted up and i'm still getting "Server error" on play store
do you think flashing the stock android over the mess i made would help? or factory reset?
Click to expand...
Click to collapse
hmm, I think I'd start from scratch, not sure where you went wrong or if my idea would have worked.
Flash stock android (an FTF) and re-root this will definitely fix things up
EDIT: try clearing play store data in settings>apps>google play
matt4321 said:
hmm, I think I'd start from scratch, not sure where you went wrong or if my idea would have worked.
Flash stock android (an FTF) and re-root this will definitely fix things up
Click to expand...
Click to collapse
ok and could you be so kind to help me find a guide to do that as well? i don't feel too confident right now, i feel i would just mess up again
is this the right guide http://forum.xda-developers.com/showthread.php?t=2648320 ?
perhaps it didn't work because i actually deleted the hosts file in etc
dakuhonoo said:
ok and could you be so kind to help me find a guide to do that as well? i don't feel too confident right now, i feel i would just mess up again
is this the right guide http://forum.xda-developers.com/showthread.php?t=2648320 ?
perhaps it didn't work because i actually deleted the hosts file in etc
Click to expand...
Click to collapse
ahh I must have missed that, deleting them was probably a bad idea
Yeah, that guide will be perfect
No worries, hope you get it sorted
matt4321 said:
ahh I must have missed that, deleting them was probably a bad idea
Yeah, that guide will be perfect
No worries, hope you get it sorted
Click to expand...
Click to collapse
that guide doesn't mention wiping data and i vaguely recall people do that when flashing roms, should i do something like that?
dakuhonoo said:
that guide doesn't mention wiping data and i vaguely recall people do that when flashing roms, should i do something like that?
Click to expand...
Click to collapse
It will wipe by default when using flashtool
Sent from my Nexus 7 2013 using Tapatalk
matt4321 said:
It will wipe by default when using flashtool
Sent from my Nexus 7 2013 using Tapatalk
Click to expand...
Click to collapse
ok, i'm going a little crazy in here, i managed to flash the stock firmware but i still can't get into play store .. so should i now do the recovery thing?
one little thing, this damned xperia doesn't have any file manager so now i can't install the things from my sd card ... what on earth am i supposed to do? i'm almost crying, how incompetent i am
dakuhonoo said:
that guide doesn't mention wiping data and i vaguely recall people do that when flashing roms, should i do something like that?
Click to expand...
Click to collapse
Many times developers don't specifically state that you must wipe data, but the fact that not doing so generally gives rise to so many errors, that I'm surprised people still "dirty flash" and complain about errors.
On the other hand, if clearing data for the play store/google framework/etc. didn't work as @matt4321 suggested, and you are still can't access the play store after flashing an FTF (and having wiped /data, obviously), then it's most likely a problem with the GAPPS that come with your FTF/ROM that you flashed (unlikely), or a problem with your internet connection.
If you have any .apk file you wish to install, and you have ADB installed on your computer, just enable USB debugging in developer settings, connect USB cable, connect to your phone through ADB (adb -d shell) and type:
Code:
cd /storage/sdcard0 (or sdcard1, or wherever your .apk file is located)
pm install name-of-your-apk.apk
Something which can also be done with a terminal emulator, which I doubt you have since you don't have access to the Play Store.
Unbelievable
i did all those things, lost all the data, everything i did with that phone so far and now i solved it by simply setting time manually and forgetting and reconnecting to my wifi, i want to sincerely thank you all for you help, namely matt4321, for keeping my hopes up, i'll try towelroot again
i mean, would you believe it? something as simple as reconnecting my own wifi
I'm experiencing some gradual slowdown with my M7 running Viper One 7, to the point where I'm clearing the caches once a week. Seems stoopit.
Since I've flashed prolly 20 ROMs over the last year, I'm thinking that it might be worthwhile to do a factory reset, wipe the SD and all.
If I make a Nandroid with TWRP and use that to start with, wouldn't that actually include any bad gris gris and therefore kind of null the point of doing the factory reset?
Would I be better off, after the factory reset, flashing the ROM and Kernel (EL-X) from scratch and dropping all else from a back-up?
Or am I over thinking this?
Something slowing my M7.
I have 140 apps. No games.
About a dozen of which are running normally, using 785mb of 1.7gb RAM.
And 27.5G of total storage used.
Wtf 140 apps? I got maybe 30.
metropical said:
If I make a Nandroid with TWRP and use that to start with, wouldn't that actually include any bad gris gris and therefore kind of null the point of doing the factory reset?
Click to expand...
Click to collapse
Probably but it might worth a try
Would I be better off, after the factory reset, flashing the ROM and Kernel (EL-X) from scratch and dropping all else from a back-up?
Click to expand...
Click to collapse
imo, yes it would be better to start over from scratch.
I have 140 apps. No games.
About a dozen of which are running normally, using 785mb of 1.7gb RAM.
Click to expand...
Click to collapse
shouldn't be an issue
And 27.5G of total storage used.
Click to expand...
Click to collapse
thats a lot, but I'm not sure its related to your issue.
Fairtex said:
Wtf 140 apps? I got maybe 30.
Click to expand...
Click to collapse
that's what I had when I bought my Sensation.
But stuff comes along ...........
alray said:
Probably but it might worth a try
imo, yes it would be better to start over from scratch.
shouldn't be an issue
thats a lot, but I'm not sure its related to your issue.
Click to expand...
Click to collapse
then away we go ......... from scratch
metropical said:
then away we go ......... from scratch
Click to expand...
Click to collapse
good luck, let me know if it worked
alray said:
good luck, let me know if it worked
Click to expand...
Click to collapse
no matter what I do, ViperOne remains as does the ElementalX kernel.
Weird
metropical said:
no matter what I do, ViperOne remains as does the ElementalX kernel.
Weird
Click to expand...
Click to collapse
what did you try ? Format Data in TWRP will completely erase the phone
then adb push a rom back to the phone and your off to a clean start
clsA said:
what did you try ? Format Data in TWRP will completely erase the phone
then adb push a rom back to the phone and your off to a clean start
Click to expand...
Click to collapse
thanks
http://forum.xda-developers.com/showpost.php?p=56964579&postcount=42028
metropical said:
thanks
http://forum.xda-developers.com/showpost.php?p=56964579&postcount=42028
Click to expand...
Click to collapse
so you have already done the Format Data ?
clsA said:
so you have already done the Format Data ?
Click to expand...
Click to collapse
I have . and in updating TWRP, I wiped the phone again.
so sideloading again.
ah well
so far, the couple apps that were misbehaving have been better.
but the 1 xPosed module I have, MacroExpansion isn't working correctly.
metropical said:
I have . and in updating TWRP, I wiped the phone again.
so sideloading again.
ah well
so far, the couple apps that were misbehaving have been better.
but the 1 xPosed module I have, MacroExpansion isn't working correctly.
Click to expand...
Click to collapse
The second you installed xPosed you screwed up in my opinion .. I have no use for it. But i understand many like it for the Sense 6 toolbox fuctions
alray said:
good luck, let me know if it worked
Click to expand...
Click to collapse
so far so good. found 1 offending app that slowed others, so it's gone.
seems to be back to what I remember.
I can no longer write any custom roms to my N6. Started with PURE 3.5 but now effects any rom i try to flash. I have brought my N6 back to factory state multiple times even relocking it. Only thing I can do is Fastboot flash N6 image from google manually piece by piece. I do have working 5.01 and phone works. Roms either hang or have errors. or just write the boot.img file. TWRP works other wise i can backup and restore, I am using 2.8.3.1. I have searched all over for a fix....
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
dipstik said:
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
Click to expand...
Click to collapse
I had no problem updating Pure for over a month from like 2.0 to 3.4.
they all hang when writing to system as far as i can tell. happens regardless of Pure....from a fresh clean image of 5.0 or 5.01 i can not flash any roms. driving me nutzo....i can no longer flash pure 3.4 either but i can restore the phone from a nandroid backup i had on my pc and run Pure 3.4 just fine.
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Pilz said:
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Click to expand...
Click to collapse
yes and both cache.....
also made sure system not mounted.
very frustrating.
Bignoze73 said:
yes and both cache.....
also made sure system not mounted.
very frustrating.
Click to expand...
Click to collapse
That is very odd, did you try reflashing TWRP or using a different version.
Pilz said:
That is very odd, did you try reflashing TWRP or using a different version.
Click to expand...
Click to collapse
mutiple times......tried all versions of TWRP too.
I can write a custom kernal like elementalx no problem.....just not roms.
Bignoze73 said:
mutiple times......tried all versions of TWRP too.
Click to expand...
Click to collapse
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Pilz said:
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Click to expand...
Click to collapse
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Bignoze73 said:
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Click to expand...
Click to collapse
If you restore your stock recovery on your phone you could try this.
Make sure TWRP is not installed on your phone and that the stock recovery is installed and working:
Have TWRP in your platform tools folder named however you want
Then use "fastboot boot recovery 'whatever you named TWRP' "
This will boot TWRP without installed it. Then try to flash the ROM using TWRP. You can also use the"adb push" to sideload the ROM onto your phone so you can find it via TWRP.
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Bignoze73 said:
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Click to expand...
Click to collapse
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Pilz said:
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Click to expand...
Click to collapse
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
laureanop said:
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
Click to expand...
Click to collapse
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Pilz said:
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Click to expand...
Click to collapse
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
laureanop said:
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
Click to expand...
Click to collapse
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Pilz said:
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Click to expand...
Click to collapse
Is there a tool or command to do a full memcheck of both ram and storage
rgraville said:
Is there a tool or command to do a full memcheck of both ram and storage
Click to expand...
Click to collapse
I'm not sure I've never had the need to do one from adb or fastboot
Pilz said:
I'm not sure I've never had the need to do one from adb or fastboot
Click to expand...
Click to collapse
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Bignoze73 said:
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Click to expand...
Click to collapse
I assume you are also out of the return window. Well if you are unlucky or lucky (depending on how you view it) you could have an issue eventually. They will RMA for burn in, camera issues etc... The camera issue was common in the earlier production models that I had. There should be another method, I would look into it if you have time.
Alright, so I had M Preview 1 and used the rooting procedure from this thread: http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285 and it worked flawlessly with no booting errors or anything.
Now that I've upgraded to Preview 2 on the day it was released I can't get it to root. I've tried the methods in that post, I've tried some other methods that I've picked up over the years of doing this kind of stuff and no matter what I end up in a boot loop or a boot validation error that just shuts the phone down. So I just end up re-flashing the system and boot partitions to get it back up again while I look for more solutions.
I've looked all over XDA and some other forums thinking that maybe I need a different kernel, or Super SU package but I can't find anything. If someone can explain to me or at least reply with a link to a thread that will help me out I'd really appreciate it.
Thanks in advance!
jonzey231 said:
Alright, so I had M Preview 1 and used the rooting procedure from this thread: http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285 and it worked flawlessly with no booting errors or anything.
Now that I've upgraded to Preview 2 on the day it was released I can't get it to root. I've tried the methods in that post, I've tried some other methods that I've picked up over the years of doing this kind of stuff and no matter what I end up in a boot loop or a boot validation error that just shuts the phone down. So I just end up re-flashing the system and boot partitions to get it back up again while I look for more solutions.
I've looked all over XDA and some other forums thinking that maybe I need a different kernel, or Super SU package but I can't find anything. If someone can explain to me or at least reply with a link to a thread that will help me out I'd really appreciate it.
Thanks in advance!
Click to expand...
Click to collapse
flash any m based custom kernel, i generally use despair or elementalx, and then flash the latest supersu, when you boot, youll have root. the latest supersu is version 2.49 btw. and if you want to yse the kernel in that thread, elite kernel, grab the latest m version, not the one in that thread, its old.
simms22 said:
flash any m based custom kernel, i generally use despair or elementalx, and then flash the latest supersu, when you boot, youll have root. the latest supersu is version 2.49 btw. and if you want to yse the kernel in that thread, elite kernel, grab the latest m version, not the one in that thread, its old.
Click to expand...
Click to collapse
Yeah I tried using the latest M version of that kernel and yes, I used Super SU 2.49. Thanks though, I'll try the latest elementalx kernel.
jonzey231 said:
Yeah I tried using the latest M version of that kernel and yes, I used Super SU 2.49. Thanks though, I'll try the latest elementalx kernel.
Click to expand...
Click to collapse
well, then its odd, you should have gotten root after flashing both in recovery.
simms22 said:
well, then its odd, you should have gotten root after flashing both in recovery.
Click to expand...
Click to collapse
I know, right? I'll give it another shot. I'm getting ready to do it now. I'll update in a few minutes when I've finished up.
Edit: Grabbed Elemental from here: http://forum.xda-developers.com/showpost.php?p=61931417&postcount=3921&nocache=1
Updated last night so it should be the absolute latest version. So I'll flash twrp in fastboot, then boot into twrp and flash the kernel first, and then supersu and I should be good to go.
The Elemental Installation is freaking awesome! I've never installed it before. That's so cool how it brings up it's own interface for the install to customize your setup.
And the phone just booted up after flashing both the kernel and supersu.
The boot animation (spinning colored dots) is glitching out though. Can't tell if it's a "setting up" type of thing or not. It's optimizing app 1 of 1 right now.
jonzey231 said:
The Elemental Installation is freaking awesome! I've never installed it before. That's so cool how it brings up it's own interface for the install to customize your setup.
And the phone just booted up after flashing both the kernel and supersu.
The boot animation (spinning colored dots) is glitching out though. Can't tell if it's a "setting up" type of thing or not. It's optimizing app 1 of 1 right now.
Click to expand...
Click to collapse
yea, elementalx uses the aroma installer, whete you can pick and chose what you wnt in the kernel. sounds like its booting, hopefully youll have root.
simms22 said:
well, then its odd, you should have gotten root after flashing both in recovery.
Click to expand...
Click to collapse
It's been in a bootloop for like 5 minutes. It would get the the Android is Starting screen and loan for about 30-40 seconds, then reboot.
Then it would hit the validation screen and reboot.
Then it would boot back to Android is Starting, freeze, and reboot lol
It is very erratic, all of this has been going on without any interference from me. Just letting it sit there trying to work through it's issues.
Then all of a sudden as I was typing "adb reboot-bootloader" the thing boots right into my existing lockscreen haha. So I guess I'll just do my best to not have to reboot this thing in case it wants to have a seizure like that again lol.
simms22 said:
yea, elementalx uses the aroma installer, whete you can pick and chose what you wnt in the kernel. sounds like its booting, hopefully youll have root.
Click to expand...
Click to collapse
It's finally up and loaded and yes, I've got root now. Thanks for your help today.
jonzey231 said:
It's finally up and loaded and yes, I've got root now. Thanks for your help today.
Click to expand...
Click to collapse
simms22 said:
Click to expand...
Click to collapse
One final question.
Is there any way to get system write access? If so, what did you use? I tried the fix_rw_boot.img that I used for preview 1 and it just put me in a boot loop lol.
jonzey231 said:
One final question.
Is there any way to get system write access? If so, what did you use? I tried the fix_rw_boot.img that I used for preview 1 and it just put me in a boot loop lol.
Click to expand...
Click to collapse
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
simms22 said:
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
Click to expand...
Click to collapse
Hmmm...I flashed Elite with SuperSU and ElementalX with SuperSU. Wasn't able to get root with either one. Clean flashes (coming from formatted partitions) each time too.
I've got it up and rooted and restored but don't have access to write to the system partition at all no matter what I try.
jonzey231 said:
Hmmm...I flashed Elite with SuperSU and ElementalX with SuperSU. Wasn't able to get root with either one. Clean flashes (coming from formatted partitions) each time too.
I've got it up and rooted and restored but don't have access to write to the system partition at all no matter what I try.
Click to expand...
Click to collapse
yea, it seems as a few are having this same issue, while most have no issue http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285/page18
simms22 said:
sure. i just flashed an m compatible kernel(despair), and supersu 2.49. bow ive root with full access, write as well.
Click to expand...
Click to collapse
simms22 said:
yea, it seems as a few are having this same issue, while most have no issue http://forum.xda-developers.com/nexus-6/general/root-nexus-6-android-m-dev-preview-t3123285/page18
Click to expand...
Click to collapse
Yeah I just flashed Despair and SuperSU to replicate what you've done and still nothing.
This is pretty irritating.
jonzey231 said:
Yeah I just flashed Despair and SuperSU to replicate what you've done and still nothing.
This is pretty irritating.
Click to expand...
Click to collapse
ok, i think i have a solution for you. its a little dirty, but its a solution i think. im running it right now, so its safe. its a basic m version 2 rom. it doesnt have many additions to it, its very basic. but i think youll get root. make a backup, i think that you could dirty flash it. or, to be safe, id wipe data. flash supersu 2.49 as well. heres the rom http://forum.xda-developers.com/nexus-6/development/rom-jdx-1-0-t3121053
simms22 said:
ok, i think i have a solution for you. its a little dirty, but its a solution i think. im running it right now, so its safe. its a basic m version 2 rom. it doesnt have many additions to it, its very basic. but i think youll get root. make a backup, i think that you could dirty flash it. or, to be safe, id wipe data. flash supersu 2.49 as well. heres the rom http://forum.xda-developers.com/nexus-6/development/rom-jdx-1-0-t3121053
Click to expand...
Click to collapse
Awesome, I didn't really he'd made a ROM for Preview 2 yet. I'll make a backup and give it a shot, thanks for pointing this out to me.
I'll let you know how it goes as well!
Update: it worked!!! I wiped the system partition and flashed the ROM. It failed the first time so I tried again after mounting the system and now I've got too with system write access!! Spread the word my friend.