Does anyone know if our Nexus 6 requires a pit file for flashing? I managed the throw my partition layout out and remove some files that I shouldn't have. I now have a device that boots but has no sensor support at all. Nothing is showing up in /dev node even when manually creating the node with BB mknod. The logcat has tons of errors all pertaining to not being able to open the require port for the sensors.
Pit file? I'm assuming you're probably coming from a Samsung device since they are the only ones to use those files. If you're unlocked I'd back up my data and flash the stock image
Sent from my Nexus 6 using XDA Free mobile app
I didnt make a backup before messing around, thinking that we would have an att dump soon. And as you can tell, yea I am used to Sammy devices. I deleted a few files and now my sensors will not work. I tried ripping /etc and /system/etc from a friends Nexus 6 but even after flashing a stock image my partition table is really messed up. Flashing a stock recovery does nothing but boot loop and the phones camera responds really slowly. I have Att sending me a new one, but who knows when that will be.
Related
[Q] Why Do I get this error "The Parameter is incorrect." Trying to Write to my Phone
I have a brand new Samsung Captivate from Rogers.
I have updated it to 2.2 using kies.
I then did the one click root.
Now when I connect it to my computer I get "The Parameter is incorrect." every time I try to copy a file or make a new directory.
I have formatted the memory from the phone and I can then copy files or make folders temporarily. Until the phone decides that it wants to throw the error again.
I can also run a check disk from my computer with “Automatically Fix system errors" and "scan for and attempt recovery of bad sectors" check. This will also fix the problem temporarily.
So how do I fix the permanently?
This is my first post so please don't flame me to bad.
Thanks in advance.
looks like something wrong in your computer. try to reinstall the usb drivers and switch to another computer to see if it still happens.
I have tried it on my desktop, my laptop and my work desktop.
The problem always reappears.
I am using the driver from the Wiki.
Windows ?????
Windows 7 x64
Parameter is incorrect error:
You need to make sure your drives (SD) are/is formated with FAT32.
This will allow maximum file size of 4Gb.
I have formated fat32 and it has just started getting the error again.
I found this post http://forum.xda-developers.com/archive/index.php/t-907854.html
this is what is happening to me.
Has anyone found a fix?
i had this issue with stock 2.2 rogers.
one time i was able to fix by right clicking the phone in my computer> properties> tools > scan for errors. Found some.
it was also deleting files/songs that i put on the internal sd.
returned the phone. no problem since, but have also been using custom roms since.
This is weird. I had the same problem on an old version of di11igafs rom. It was related to the file vold.fstab which deals with mounting storage. I find it odd that this is happening o a sock rom. If any of you feel so inclined upload your vold.fstab and ill have a look.
HaiKaiDo said:
If any of you feel so inclined upload your vold.fstab and ill have a look.
Click to expand...
Click to collapse
I will upload my vold.fstab if you tell me where to find it.
Sent from my SAMSUNG-SGH-I896 using XDA App
Trusselo said:
returned the phone. no problem since, but have also been using custom roms since.
Click to expand...
Click to collapse
Did you return the phone ti rogers?
Sent from my SAMSUNG-SGH-I896 using XDA App
If you use root explorer or ASTRO (which is free) to navigate to the root directory of your phone, look for the folder named 'etc' inside that folder should be 2 VOLD files. make a copy of these.
PS: MAKE SURE NOT TO MOVE THEM!!! xD (or delete O: )
So I just got off the phone with samsung and they told me to return the phone to rogers because rogers website is giving the wrong firmware.
Now I do not know if this is true but I would like to fix the problem.
They also said that I can not put the correct 2.2 on as kies will see the wrong 2.2 and not install the correct one.
So now I guess I have no choice
I have attached both of the vold files for you to look at.
I hope someone can come up with a fix as Rogers does not want to change the phone. They are waiting on a fix from Samsung and Samsung says there is no fix coming and that I need to change the phone.
Is there a way to go back to 2.1 Rogers?
windburn said:
I hope someone can come up with a fix as Rogers does not want to change the phone. They are waiting on a fix from Samsung and Samsung says there is no fix coming and that I need to change the phone.
Is there a way to go back to 2.1 Rogers?
Click to expand...
Click to collapse
use odin 1.7 with
http://dl.dropbox.com/u/19201431/SGH-I896_UXJI2StockRogers2.1.zip
to get back to 2.1 rogers. use the PIT file and RE-Partition. i have been flashing phoenix roms with no problem.
i only had those error problems with stock 2.2 after updating, but to be honest only had the phone less than 1 week between 2.1> 2.2>custom> returned to store. the second phone was on phoenix within 2 hours of getting it.
Well, now that we can use clockwork recovery, we can start trying to figure out why a nandroid restore causes the Kyocera splash screen to be replaced by a whit horizontal bar.
Anyone have any suggestions?
My assumption would be that the Kyocera splash screen is hardcoded into the phones "hidden files" and when you flash Clock work and do the Nandroid restores it is probably overwritting them.
Been searching on the net for any instance of a similar issue, to no avail (yet).
Hidden files hmm? Mind elaborating?
Spz0 said:
Hidden files hmm? Mind elaborating?
Click to expand...
Click to collapse
lol I say this b/c we cant find these files anywhere and almost every OS whether it be a computer or a phone has "hidden files" that the user cannot access. These files usually hold important system information that if altered would likely result in unstable operation or even the lack of operation. These files are normally stored on a partitioned part of the "disc" that is not accessible. When I used to develop for the Jailbreak community on the iphone we ran into this a lot. Of course there is almost always a work around when it comes to modding/hacking.
I am trying to learn as much as I can about Android OS and so far I can say it is very, very different than the iphone OS.
I am pretty sure the image is in the boot loader.
There is a 4K header, but only the first 2K are used. Then after that the boot files start.
I can rip the boot loader with either doing a "cat /mtd > file.img" (or something like that, don't remember off hand), or with the dump_image program.
If I use the cat, I get a white bar, if I use dump_image, I get a black screen. dump_image removes empty sectors I believe. That's the difference so it must be in those sectors.
On top of that, if I flash the sprint boot loader, I get a Sanyo image. So basically, someone needs to go in there with a hex editor and manually copy whatever is needed into that useless space after the first 2K and the 4K. At least that's where I think it is. Someone could do a compare between the dump_image and the cat to be certain.
(That's all from what I remember from a few months ago)
But to know what needs to be copied, we need to somehow get a fresh copy of the raw 2.2 upgrade files. Not certain how to go about that. Since the OTA upgrade downloads them, we should be able to adb and copy them over before it installs them, depending on where it's being downloaded to.
phazei said:
But to know what needs to be copied, we need to somehow get a fresh copy of the raw 2.2 upgrade files. Not certain how to go about that. Since the OTA upgrade downloads them, we should be able to adb and copy them over before it installs them, depending on where it's being downloaded to.
Click to expand...
Click to collapse
Would any of the files from the zclusive pc update route be of any help? I still have those.
I'm not really sure if this is any help at all, but in normal linux distros the initrd.gz is stored in the boot partition. This archive contains scripts used to boot the computer. It has been known to contain image files. I do not have the necessary OS right now to gunzip and investigate. If you guys want to find out if that file exists on android and see what is inside, it might be a good lead. If nothing else, it may point to the correct image.
I hace CentOS Ubuntu and a few other live distros, Ill check the boot partition for the kyo logo.
Sent from my Zio using XDA Premium App
NO MORE WHITE BAR!
Mattix724 said:
So, I have dumped my boot.img finally because gregnotcraig and other devs restored with nandroid and lost the Kyocera splash. With this boot image below you can restore your Kyocera splash. NO MORE WHITE BAR.
http://db.tt/zisPRYH
Simply enter fastboot and place this boot image in your SDK folder where fastboot is located.
Run this command...
"fastboot flash boot boot.img"
"fastboot reboot"
And there you have it, the stock splash screen.
Sent from my Zio using XDA Premium App
Click to expand...
Click to collapse
Sent from my Zio using XDA Premium App
i said it in #openzio, but i'll say it here, too...
thank the dog you had that. you made several people in irc happy little campers!
Solved!
http://forum.xda-developers.com/showthread.php?t=994754
Mattix724 said:
NO MORE WHITE BAR!
Sent from my Zio using XDA Premium App
Click to expand...
Click to collapse
For those of us who would like to change up the Kyocera logo, would it be possible to flash the Sprint ZIO boot.img to a cricKet ZIO (and not lose functionality)?
No.
Sent from my Zio using XDA App.
We will be releasing a custom boot image soon. Source is available just need to recompile with new splash1
Sent from my Zio using XDA Premium App
I have a Dell Streak 7 WIFI and made a real newbie mistake that I have not made since owning a Moto Droid A855. I did not make a back up of the system while I was tinkering, didn't plan on doing custom roms, and now the unit boots up after a factory data reset but I cannot get it past the language selection. I was removing APK's that I did not need and obviously went to far. I know dumb on my part and I know better. Can anyone help? All of the links to the needed files seem to be gone or dead. Thanks!
I forgot to mention the obvious, 3.2 rooted.
I was able to finally find the package downloads that were unavailable to most of us but the recoveries are not there. Can anyone help?
Download the latest PKG from here:
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak_7#Official
rename it update.pkg and save it to an external SD card.
Make sure your tablet is fully charged, boot into recovery mode.
Choose: Software upgrade via update.pkg on SD card
You should be back in business.
Those links are dead but i found the files thanks to TheManii. Problem is the update does not go says it is up to date and I still cannot get past the language selection. I'm thinking I need to push the system image by ADB and see how that goes.
Ok found the files thanks to Manii. Takes the system image, boot image and the restore image and flash them with ADB. Works like a charm.
Sent from my Dell Streak 7 using xda app-developers app
Hello
I've got the Note 5 SM-N9208 and I am trying not to root (tripped Knox tho as I but Phillippines system.img on it) it as the annoying Barclays App doesn't work.
I am however, trying to add my custom CA certificate into the /system/etc/security/cacerts folder. This is what I used to do in my rooted devices before and worked fine.
I have flashed TWRP and taken a full backup (thank God!) and then mounted the system as RW, copied the file, rebooted and voila, boot loop on the Samsung Note 5 screen.
The only fix is to reflash the system partition from the original TAR file which makes me wonder - is there a mechanism that prevents system from being modified if the device is unrooted? Something like Samsung's system protection or something.
Could anyone try to reproduce the issue on an unrooted phone just to see if it's just me being unlucky? Or is is simply not possible to modify system without root? If so, how come TWRP allows me to do so?
Let me know what you think guys
Looking forward to hear someone else's opinion.
mateuszd said:
Hello
Let me know what you think guys
Looking forward to hear someone else's opinion.
Click to expand...
Click to collapse
You must be rooted to make system changes.
You need to make some changes in ramdisk : remove support_scfs,verify from the fstab files for system partition
I have a rooted Nexus 6 and wanted to edit my build.prop file in order to enable Wifi sharing. I made a backup first, and then when I saved build.prop after editing it was 0 bytes. Then I saw the backup was 0 bytes. First I crapped myself, then I copied in a N6 specific build.prop I downloaded off the net to /system, but no matter what I did, that new file was 0 bytes even though the original was 5k. 'df' showed I was not out of space in /system (had about 1.5 meg free). I even tried mounting /system RW just in case it was RO.
I finally decided after 3 hours of this that perhaps the whole thing was RO and a reboot would clear everything (based on a couple of other posts I read).
I held my breath, rebooted..... and as I feared I just get the black screen that says Google with a lock.
I can't shut off the phone (to reboot into recovery mode), the Nexus doesn't have an off button. I hold power down and it reboots. I give it a short press and it does nothing. I hold them all down and it reboots.
Can I get a pointer please to a thread that might help bail me out?
As a side note, I'm having problems connecting to my phone in debug mode with adb (even before the reboot), so if I need to use those tools, that's another hurdle I'll have to figure out.
Hold the power button + volume down to get to the bootloader. Go to recovery and reflash whatever rom you were on . A dirty flash should suffice.
Hit thanks if this solve your problem.
Getting a little further. Managed to boot into TWRP. Got into terminal, tried to copy in the build.prop file to /system that way but am being told I'm out of space.
Found a similar thread here I'm digging through.
http://forum.xda-developers.com/nexus-6/help/nexus-6-bootloops-build-prop-edit-6-0-1-t3473306
Just saw post #2, thanks. Thought I had it. I freed up some space in /system/app by deleting a couple of foreign keyboard files. Then copied in the build.prop file and this time it was the correct file size. Rebooted, but no change. I really thought that would have fixed things.
As an aside, df lies, there really was no space in /system
Looks like what I found was not a stock build.prop. I have no idea how much it differs but it contains this line:
ro.build.display.id=NexZen by VECTUS V07
Ha! Also it's for 5.1.1. Darn! I should have looked at this first.
Does anybody happen to have a pointer to a stock Nexus 6 6.0.1 build.prop? Google has failed me on this one.
Your original problem was, as you've found, that you had no space in your system partition. The reported 1.5 mb is way to little space to do any kind of system mods... I've found i need at least 50-60 mb free.
Stock build.prop is easiest found in the factory images, in system.img. If you're pushing it to your phone in recovery, don't forget to set the correct permissions (chmod 644).
Thanks, I did pull the file out of the stock ROM, but I must have gone wrong somewhere because it didn't work. I then looked at the /system directory and it was empty other than /system/bin. No idea how the heck I could have deleted the other files in there. That would have been a nice clean fix. But now I'm forced to do a flash. What a waste of a night! Thought it would be nice and simple to turn on wifi sharing. Ha!
I figured 1.5MB would be more than enough to add a single line to a file, the file system block size I'm guessing is in the 2-4K neighborhood. Regardless, it clearly wasn't enough for whatever reason.
I was on a stock ROM. Since I can't easily do a dirty flash of a stock rom, and I can't connect with adb, I need to try to find a TWRP version of a stock 6.0.1 or something really close. I'm pulling off whatever data I can save now just in case I have to wipe this.
If your /system is empty in TWRP it means you haven't mounted system. Under "Mount", make sure "system" is checked.
Sounds like the easiest thing for you would be just to fastboot flash the system.img from the factory image. That'll get you back on track.
It was a really late night but I'm back in business this morning. I used this stock ROM image with TWRP and did a dirty flash.
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-6-0-1-mmb29k-t3279185
Now I still need to update my friggin build.prop!!!
robroth said:
It was a really late night but I'm back in business this morning. I used this stock ROM image with TWRP and did a dirty flash.
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-6-0-1-mmb29k-t3279185
Now I still need to update my friggin build.prop!!!
Click to expand...
Click to collapse
Use adb and pull it to PC,edit it and push it back easiest way with newer Android versions
i have encountered this on my newer nexus 6. whereas my older nexus 6 seems to be void of these characteristics.(i have started to believe it is because the older one was moved through the API levels smoother....19-20-21-22-23-24-25....as my new one has gone from 18--------to 25. THAT IS TOTAL PROCESS OF ELIMINATION. no idea if thats what it is.) i was able to to push a reboot and temp. flash into twrp from adb/nrt. i dirty flashed my ROM and GApps and seemed to quick fix.
---------- Post added at 03:54 PM ---------- Previous post was at 03:47 PM ----------
there are a few key issues i have witnessed (as a whole) with a young and older sibling too..... which is not the subject of this issue but i think what i have come to learn can shed light on situational(from time to time) issue that i have to deal with when consistent flashing. the RO/RW is now a part of my routine for the newer phone(cause it will randomly drop its RW for no reason and prevent proper filing for busybox or in my case nethunter libraries)
whew. I was gritting my teeth on reboot tonight after editing build.prop again, but this time it went without a hitch. It sucks how you can find all these great articles about how to do stuff, but invariably I own the one phone where there's a gotcha that one doesn't think to look for
I'll keep an eye out for if/when it'll let persist.root. or the .....persist.dun. Will set =1 without breaking selinux.