Related
Here is the OTA update zip.
http://www.androidfilehost.com/?fid=22946563261203148
d0c70dc593bdd729b14688a1be473102
http://tinyw.in/RwRh
d0c70dc593bdd729b14688a1be473102
Dammit, beat me to the punch lol. Thanks bud!
Sent from my SPH-L720 using Tapatalk 2
1) install update
2) adb pull /proc/config.gz
3) extract using 7zip/winrar etc
4) open config with wordpad
5) copy all and paste to pastebin.com
6) control + f setuid
that will tell ya if the switch has been flipped or not
shabbypenguin said:
1) install update
2) adb pull /proc/config.gz
3) extract using 7zip/winrar etc
4) open config with wordpad
5) copy all and paste to pastebin.com
6) control + f setuid
that will tell ya if the switch has been flipped or not
Click to expand...
Click to collapse
Will do. Running a backup right now and will install after that.
Putting stock back on.
Wiping Data
Installing update
Yep it is blocked.
crawrj said:
Yep it is blocked.
Click to expand...
Click to collapse
k gimme about 40-50 mins and ill have a workaround. mind posting that config file btw?
you planning on doing a rooted odex/deodex'd rom?
shabbypenguin said:
k gimme about 40-50 mins and ill have a workaround. mind posting that config file btw?
you planning on doing a rooted odex/deodex'd rom?
Click to expand...
Click to collapse
Yeah I plan on it. Attached the gz.
Pulling source now to run a diff and see what has changed in kernel beyond the obvious.
Be interested to see if they left that in the defconfig since they know someone will probably flip it back.
anyone check to see if kies would update em? would be a nice thing to have the tar for it as well
Just to confirm the obvious rooting did not work.
Installing the stock MDC kernel allows rooting.
if you dont mind, have mdl kernel installed, flash cwm/twrp. boot into recovery and dd the kernel. i wish to compare ramdisks
Well, that diff was actually productive.
They have made the change in the common defconfig for all i9505 variants.
So expect this to be coming to the rest of them soon.
Looks like on the kernel side a majority of the changes are to 3 files:
firmware/ssp_rev03.fw.ihex
firmware/tsp_synaptics/synaptics_b0_5_1.fw.ihex
firmware/tsp_synaptics/synaptics_b0_5_1_fac.fw.ihex
Beyond those 3, many of the changes pertain to ATT and EUR variants.
Attaching a zip of the diff file for reference as I'll be spreading the word.
Guess I'll get with Agat to make an MDL kernel with that flipped off...
*Update 2* As Shabby mentioned, only Tmo and Sprint have seen this so far... so AT&T results can be ignored.
www.shabbypenguin.com/OUDstuff/Sams...-Kernel/TW/Stable/Stock-MDL-Stable-spr-TW.zip
sorry for teh delay, had to make breakfast for my daughter this is a MDL source built kernel, but with MDC ramdisk until i can get MDL ramdisk. it will allow root however
shabbypenguin said:
if you dont mind, have mdl kernel installed, flash cwm/twrp. boot into recovery and dd the kernel. i wish to compare ramdisks
Click to expand...
Click to collapse
The boot.img is in the update.zip already. Or do you still need it DD?
crawrj said:
The boot.img is in the update.zip already. Or do you still need it DD?
Click to expand...
Click to collapse
oh didnt know they included a full one. i didnt download the update.zip (doesnt do me any good )
ok recompiling now, seems only a minor edit in ramdisk but may be worthwhile to include it. new kernel is up at same old link crawj you have permission if youd like to include it in a odex/deodex'd rootable zip rom
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
garwynn said:
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
Click to expand...
Click to collapse
I haven't looked at the at&t threads but I would say they are wrong. You can install root but the kernel kills it. So it won't run. I have tried all three methods of install and it doesn't work.
1. Installing custom recovery and flashing supersu
2. Oding CFAutoRoot
3. Moto
shabbypenguin said:
oh didnt know they included a full one. i didnt download the update.zip (doesnt do me any good )
ok recompiling now, seems only a minor edit in ramdisk but may be worthwhile to include it. new kernel is up at same old link crawj you have permission if youd like to include it in a odex/deodex'd rootable zip rom
Click to expand...
Click to collapse
So you have the new kernel working? Where is that same old link again And thanks!
garwynn said:
Well, may not be as bad as we read a few days ago.
AT&T threads saying motochopper still working - we'd have to test CF Auto Root.
Also OTA Root Keeper supposedly working.
In the end I'll just flash a kernel that plays nice. Thanks Shabby!
Click to expand...
Click to collapse
crawrj is correct, its not a matte rof re-rooting its the binary is being killed as it tries to launch. att didnt get it in an update yet, only tmo and sprint for the us carriers.
crawrj said:
So you have the new kernel working? Where is that same old link again And thanks!
Click to expand...
Click to collapse
http://www.shabbypenguin.com/OUDstu...-Kernel/TW/Stable/Stock-MDL-Stable-spr-TW.zip
I have not rooted yet and im trying to push the OTA update now. once it goes through, you want me to try one of the rooting methods???
So i've noticed in most of the rom threads that people are needing to flash the boot.img? Is this a new boot.img? i've searched but obviously used the wrong keywords or something becuase i can't find any information on it anywhere. Can someone point me in the right direction? I remember having to do this with my Nexus 4, but links were posted everywhere for it,..
thanks in advance
Well..
The boot.img was required to be flashed separately at some point. Later one of the devs figured out how to do it using a script.
In most of the new custom roms, its within the zip and the script installs it automatically. You can see it if you open up the zip. I didnt have to flash it separately while installing trickdroid.
watermelun said:
The boot.img was required to be flashed separately at some point. Later one of the devs figured out how to do it using a script.
In most of the new custom roms, its within the zip and the script installs it automatically. You can see it if you open up the zip. I didnt have to flash it separately while installing trickdroid.
Click to expand...
Click to collapse
+1 never flashed a boot.img for this phone
boot.img is the kernel
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.
Looking for latest "stock image" for MRA58R pre rooted and forced enc disabled
Hi,
I have looked at the ROMs in Android Development sub forum but can only find heavily modified ROMs based of MRA58R. I want it stock but pre rooted and no forced encryption.
I have Nexus 6.
Regards
Stian
If you can't find one, why not take the alternative simple route of installing stock (full wipe), then flash modified no-encrypt boot and then supersu?
I flashed doitright's boot.img, booted into Android and then installed his supersu.apk. Incredibly simple. Even though he clearly states that it's a work in progress it has worked flawlessly for me for the past couple of weeks. Unencrypted and rooted.
http://forum.xda-developers.com/nexus-6/general/root-t3231211
Post 2 on the first page has the instructions and the link.
strips said:
.....MRA58R. I want it stock but pre rooted
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3059493
Using this as 'stock rooted' and works also with franco's kernel r34. Dev @Danvdh has updated this Rom with the latest security updates.
dahawthorne said:
If you can't find one, why not take the alternative simple route of installing stock (full wipe), then flash modified no-encrypt boot and then supersu?
I flashed doitright's boot.img, booted into Android and then installed his supersu.apk. Incredibly simple. Even though he clearly states that it's a work in progress it has worked flawlessly for me for the past couple of weeks. Unencrypted and rooted.
http://forum.xda-developers.com/nexus-6/general/root-t3231211
Post 2 on the first page has the instructions and the link.
Click to expand...
Click to collapse
Thanks. Doing it my self is always an alternative. I just need to find the time to do it
NLBeev said:
http://forum.xda-developers.com/showthread.php?t=3059493
Using this as 'stock rooted' and works also with franco's kernel r34. Dev @Danvdh has updated this Rom with the latest security updates.
Click to expand...
Click to collapse
Thanks but his rom had modifications I could do without. I like to have 100% stock rom but rooted and no encryption.
strips said:
Thanks. Doing it my self is always an alternative. I just need to find the time to do it
Click to expand...
Click to collapse
Although we do provide the technical details to DIY, we also provide prebuilt binaries built directly from our provided source. See first LINE of the second post.
strips said:
Thanks but his rom had modifications I could do without. I like to have 100% stock rom but rooted and no encryption.
Click to expand...
Click to collapse
This rom has that all. The gapps that were removed are in the play store.
doitright said:
Although we do provide the technical details to DIY, we also provide prebuilt binaries built directly from our provided source. See first LINE of the second post.
Click to expand...
Click to collapse
Yes, that's is what I was thinking about when I would do it myself I'm lazy but seing that it is not that many more steps to have a stock rooted phone. Thanks!
NLBeev said:
This rom has that all. The gapps that were removed are in the play store.
Click to expand...
Click to collapse
First it doesn't have stock kernel,
Latest stable hC kernel
Click to expand...
Click to collapse
Then it has some addons not giving me any value exept a possible source of errors. The missing Google Apps are only a annoyance as I use most of them.
strips said:
First it doesn't have stock kernel,
Click to expand...
Click to collapse
I understand where you are looking for. Only doubt if you will find that.
NLBeev said:
I understand where you are looking for. Only doubt if you will find that.
Click to expand...
Click to collapse
At least not yet
I have been looking for the same thing. Seems like before Marshmallow I could always count on seeing a clean, stock, rooted and decrypted ROM I could flash. Just being lazy I know, but oh well.
dakidhurricane said:
I have been looking for the same thing. Seems like before Marshmallow I could always count on seeing a clean, stock, rooted and decrypted ROM I could flash. Just being lazy I know, but oh well.
Click to expand...
Click to collapse
decrypted.. you do realize that its encrypted/decrypted via kernel, not rom right? and even if it is decrypted, its you yourself that has to go through the action of reformatting all your data before you are actually decrypted.
simms22 said:
decrypted.. you do realize that its encrypted/decrypted via kernel, not rom right? and even if it is decrypted, its you yourself that has to go through the action of reformatting all your data before you are actually decrypted.
Click to expand...
Click to collapse
I am fine with that. Everything I need is backed up somewhere else. Honestly decryption isnt that big of a deal, its just what I got used to flashing.
simms22 said:
decrypted.. you do realize that its encrypted/decrypted via kernel, not rom right? and even if it is decrypted, its you yourself that has to go through the action of reformatting all your data before you are actually decrypted.
Click to expand...
Click to collapse
I think he only means a ROM that's not enforcing encryption
strips said:
I think he only means a ROM that's not enforcing encryption
Click to expand...
Click to collapse
Yeah a lot of people know this means a rom that packs a boot.img that has ramdisk with the fstab.shamu with the data partition mount options changed from forceencrypt to encryptable, but still can be misleading to the less tech savvy readers who might misunderstand it, and believe that encrypting is in the rom part of the flashable zip file.
This is a step in the right direction
http://forum.xda-developers.com/nexus-6/development/rom-stock-mra58r-gapps-custom-stock-t3254496
It is quite easy just to flash stock images and then flash modified boot.img, twrp recovery and SuperSu. Sure, It is few more click and commands, but it's really that simple...done in a minute...
And for Kernel I am using this one. It is stock one (no encryption) with some added features like vibration control.
Link
Gapps
Tools, Tips & Tutorials
Fredo2000 said:
Link
Gapps
Tools, Tips & Tutorials
Click to expand...
Click to collapse
What's the point of those two threads you created? There is already a thread for MIUI7 and things related to MIUI. And why a second thread for Gapps? Its exactly the same link as the link you provided here...
And MIUI7 for the Nexus 5 has been out for some time. I just don't understand why you made a thread for this, there is already one.
Mr.FREE_Bird said:
What's the point of those two threads you created? There is already a thread for MIUI7 and things related to MIUI. And why a second thread for Gapps? Its exactly the same link as the link you provided here...
And MIUI7 for the Nexus 5 has been out for some time. I just don't understand why you made a thread for this, there is already one.
Click to expand...
Click to collapse
Just thought it would be cleaner, the other thread is hard to follow
Fredo2000 said:
Just thought it would be cleaner, the other thread is hard to follow
Click to expand...
Click to collapse
Ah, Okey... well I think it won't really make a difference. Soon or later this will turn into the same thread. Probably turns into a "ask for help thread" because there are always some newbies asking for help who just don't search in the thread for the same questions. ( nothing wrong with newbies, don't get me wrong )
Is this the stable one or developer version?
Developer version.
Miui7 Marshmallow, Nexus 5.
someone already installed this miui7 Nexus 5 ?
eltonpestana said:
someone already installed this miui7 Nexus 5 ?
Click to expand...
Click to collapse
Yes I did and it runs pretty well for a Dev version, just give it a try if running into some small problems isn't a big issue for you.
It's good enough for a daily driver.
eltonpestana said:
someone already installed this miui7 Nexus 5 ?
Click to expand...
Click to collapse
Yes ! Work fine on my Nexus.
Miui7 Marshmallow, Nexus 5.
but reflash gapps everytime it updates, oh my....
Sent from my Nexus 5 using Tapatalk
Nexus 5 MIUI 6.3.31>
after install version 6.3.31 the NFC function disappeared from settings> more... menu.
Was asked about also in xiaomi.eu forum but w/o any answer will be readded or not.
Mr.FREE_Bird said:
Yes I did and it runs pretty well for a Dev version, just give it a try if running into some small problems isn't a big issue for you.
It's good enough for a daily driver.
Click to expand...
Click to collapse
Kikatdroid said:
Yes ! Work fine on my Nexus.
Miui7 Marshmallow, Nexus 5.
Click to expand...
Click to collapse
khanhlinh said:
but reflash gapps everytime it updates, oh my....
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i cant install this rom with twrp 3.0.0.0, already tried cwm recovery 6.0.4.5 but the result is still the same. which recovery do you guys use?
the error is::
mount: no partition named "/dev/block/platform/msm_sdcc. 1/by-name/userdata"
target: Android/aosp_hammerhead_fp/hammerhead:6.0/MRA58K/6.4.21:user/release-keys
ivanferdino said:
i cant install this rom with twrp 3.0.0.0, already tried cwm recovery 6.0.4.5 but the result is still the same. which recovery do you guys use?
the error is::
mount: no partition named "/dev/block/platform/msm_sdcc. 1/by-name/userdata"
target: Android/aosp_hammerhead_fp/hammerhead:6.0/MRA58K/6.4.21:user/release-keys
Click to expand...
Click to collapse
Maybe flashing the factory image with fastboot will solve that partition problem. I used TWRP 3.0.2.0 to flash MIUI7. Don't forget to unmount the /system partition before you flash MIUI in TWRP, because if you leave /system mounted you will get an error. I hope this will help for you. (You can also try to wipe /data, /system, cache and dalvik-cache instead of flashing the factory image and flash MIUI7 with the /system partition umounted. If that doesn't solve your problem I suggest you to start clean with flashing the factory image and try again with my tips. Don't forget to make a backup of your important files because if you use the automatic flash process with the factory image it will wipe your whole internal storage.) Good luck :good:
No service/data after restart...?
Sent from my Nexus 5 using XDA-Developers mobile app
contakt
hove sonic google contact
ivanferdino said:
i cant install this rom with twrp 3.0.0.0, already tried cwm recovery 6.0.4.5 but the result is still the same. which recovery do you guys use?
the error is::
mount: no partition named "/dev/block/platform/msm_sdcc. 1/by-name/userdata"
target: Android/aosp_hammerhead_fp/hammerhead:6.0/MRA58K/6.4.21:user/release-keys
Click to expand...
Click to collapse
I do also have this error. When I rebooted after the installation. It just worked fine
Probably it is just some problem in the script. Let's see if MIUI will fix this
Btw, I recommended you to use RACER kernel with this rom. It is such a good combo
jeffreyvh said:
I do also have this error. When I rebooted after the installation. It just worked fine
Probably it is just some problem in the script. Let's see if MIUI will fix this
Btw, I recommended you to use RACER kernel with this rom. It is such a good combo
Click to expand...
Click to collapse
What TWRP are you using what version? Im on 3.0.0 too and keep getting error in zip
i cant install this rom with twrp 3.0.0.0, already tried cwm recovery 6.0.4.5 but the result is still the same. which recovery do you guys use?
the error is::
mount: no partition named "/dev/block/platform/msm_sdcc. 1/by-name/userdata"
target: Android/aosp_hammerhead_fp/hammerhead:6.0/MRA58K/6.4.21:user/release-keys
Click to expand...
Click to collapse
Same here, the installation eventually finishes after ~15mins but then phone gets stuck at google logo with TWRP claiming no OS is installed. I'm using TWRP 3.0.2.0, tried CWM 6.0.4.5 - same thing happens.
jeffreyvh said:
I do also have this error. When I rebooted after the installation. It just worked fine
Probably it is just some problem in the script. Let's see if MIUI will fix this
Btw, I recommended you to use RACER kernel with this rom. It is such a good combo
Click to expand...
Click to collapse
Youre right i get the no partition error too but if you wait long enough i also get script suceeeded
which is the best kernel for this rom which supports fast charge and good battery life..... pls suggest
---------- Post added at 05:11 AM ---------- Previous post was at 05:10 AM ----------
how can reduce the size of nav bar???