[REQ] /sys/devices/virtual/sensors on 4.4.2 - Galaxy Note 3 Q&A, Help & Troubleshooting

/sys/devices/virtual/sensors
Whole sensors folder would be needed... to fix my buggy kitkat.

Anyone ?

RawR Cheeze said:
Anyone ?
Click to expand...
Click to collapse
Hi, did you got the folder? My sensors are all dead and I have finally concluded that my drivers are missing from /sys/devices/virtual/ folder.
Can you please help, if you now have them in your device?

The /sys folder is a dynamic folder created by the kernel at boot. You can't just replace it.
Sent from my leanKernel 3.2 powered stock 4.4.2 (NF1) SM-N900T

toastido said:
The /sys folder is a dynamic folder created by the kernel at boot. You can't just replace it.
Click to expand...
Click to collapse
Can you please suggest any solution? Or at least guid me to ensure if my sensor H/W has gone bad or its some S/W issue.
All i can remember is i flashed a wrong boot file (from some old version of CM11 nightly) on boot there were a lot of errors, com.phone... Etc stopped working. Then I flased the actual boot.img and all was good again. Didn't checked the sensors then. Latter same day my phone died of battety while i was playing a game. After restart I got to know none of my sensors are working... :crying:

Related

[Q] Blue Screen

Hello. I am scared. Saw pink screen. Blue screen is only coming while I try to boot. When I plug it with PC one drive comes nothing inside it. Will I be able to use my phone ever again? I think by mistake I wiped my Mobile drive. Can anyone save me? please guide.
Moderators. Sorry for starting this thread. I could not find solution for U8800 in other threads.
get the bootloader files and put them in ur phone when in pink mode..
u have to state what ur phone model and rom version are so that somebody may be able to provide u with the right files..
thx
iamelton said:
get the bootloader files and put them in ur phone when in pink mode..
u have to state what ur phone model and rom version are so that somebody may be able to provide u with the right files..
Click to expand...
Click to collapse
Thanks for the help. But I don't know what exactly you said. Can you please upload All bootloader files in a zip. My model is Huawei Ideos X5 U8800. Please help. I am really stuck and scared. for ROM version.. That is where I got stuck I was installing CM7 and by mistake I formatted everything. So do idea which ROM to write here. And I do not know the folder structure so please upload entire thing in zip or do guide me . thanks in advance
there are U8800, U8800H, U8800-51, U8800 Pro/+, and may be more..
and there are android 2.2 and 2.3 stock roms..
every combination of them has a different set of bootloader files, so giving u a wrong set of files will not help at all..
u got to get this info first before someone can help u..
maybe at least u can tell where u got the phone, any info printed on the box, etc..
iamelton said:
there are U8800, U8800H, U8800-51, U8800 Pro/+, and may be more..
and there are android 2.2 and 2.3 stock roms..
every combination of them has a different set of bootloader files, so giving u a wrong set of files will not help at all..
u got to get this info first before someone can help u..
maybe at least u can tell where u got the phone, any info printed on the box, etc..
Click to expand...
Click to collapse
I have U8800 I have bought from India. It was having 2.2.1 and was trying to update on 2.3.7 CM. Is this information sufficient? please help
You formatted everything?
NEVER format boot. I suggest you reflash firmware.
Sent from my U8800 using Tapatalk 2
Qqqxxxzzz said:
You formatted everything?
NEVER format boot. I suggest you reflash firmware.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
How to do that? any help for that?
i think thats enough..
unfortunately i just have a backup of stock 2.3 rom's bootloader files, and my phone is U8800H..
well wait for somebody to come up then..
cr723 said:
Hello. I am scared. Saw pink screen. Blue screen is only coming while I try to boot. When I plug it with PC one drive comes nothing inside it. Will I be able to use my phone ever again? I think by mistake I wiped my Mobile drive. Can anyone save me? please guide.
Moderators. Sorry for starting this thread. I could not find solution for U8800 in other threads.
Click to expand...
Click to collapse
u have probably deleted ur boot.img from phone's custom folder
there is only one way out
download the file i have provided in the link
extract the rar file using winrar
copy the "dload" folder to ur sdcard (dont put it in any other folder, just paste it in the sdcard)
pull out the battery and put it back
and then while holding volume + key switch on the mobile until it shows update on the screen
note: u need to have other mobile or sdcard reader to put dload folder in ur sdcard.... u cant access r sdcard while being in bluescreen of ur u8800
enjoy
http://server.streznik.org/Stock ROMs/U8800 V100R001C00B138SP04%28Normal%29.rar
Thanks All, finally I am able to solve it. Here is what I did incase in future some1 has same issues.
when I formatted my mobile last time (a year ago), (by mistake) I took backup of stock rom images.
amss.mbn
boot.img
EMMCBOOT.MBN
recovery.img
I created a folder called Image and copied all 4 in that folder. Now my Blue screen is converted into Pink one. on my other SD card i put 2.2.1 stock in "dload" folder.
I installed foryo normally by pressing power button and volume keys
I went in pink mode again to copy CWM image.
I went to CWM and installed CM7 (geno) I don't know I tried 10 times to install ezet. It is not at all working with me. anyway But m very happy to be back to CM7 after using ICS MIUI (very much ram hungry).
Thanks everyone for helping me out.
It cant mount sd card, i cant format sd card and now i have blue screen error. By mistake i deleted everything I made a file image and put amss.mbn
boot.img
EMMCBOOT.MBN
recovery.img
to in it but still cant oopen phone What will i do?
Cursed Chico said:
It cant mount sd card, i cant format sd card and now i have blue screen error. By mistake i deleted everything I made a file image and put amss.mbn
boot.img
EMMCBOOT.MBN
recovery.img
to in it but still cant oopen phone What will i do?
Click to expand...
Click to collapse
Do you have back up of your image folder? if not let me know I will upload mine
cr723 said:
Do you have back up of your image folder? if not let me know I will upload mine
Click to expand...
Click to collapse
No. I lost it. I only have recovery.img and boot.img adn i dont know where to load this. Because i cant mount my internal sd card.
He formatted emmc partition. You can boot to cwm tho. Any got spare pink screen?
Sent from my u8800-51 using xda premium.
cr723 said:
Thanks All, finally I am able to solve it. Here is what I did incase in future some1 has same issues.
when I formatted my mobile last time (a year ago), (by mistake) I took backup of stock rom images.
amss.mbn
boot.img
EMMCBOOT.MBN
recovery.img
I created a folder called Image and copied all 4 in that folder. Now my Blue screen is converted into Pink one. on my other SD card i put 2.2.1 stock in "dload" folder.
I installed foryo normally by pressing power button and volume keys
I went in pink mode again to copy CWM image.
I went to CWM and installed CM7 (geno) I don't know I tried 10 times to install ezet. It is not at all working with me. anyway But m very happy to be back to CM7 after using ICS MIUI (very much ram hungry).
Thanks everyone for helping me out.
Click to expand...
Click to collapse
Can you, please, make an archieve with these files and share it with us? I've lost my backups when my PC died some time ago.
Hey please reply
cr723 said:
Thanks All, finally I am able to solve it. Here is what I did incase in future some1 has same issues.
when I formatted my mobile last time (a year ago), (by mistake) I took backup of stock rom images.
amss.mbn
boot.img
EMMCBOOT.MBN
recovery.img
I created a folder called Image and copied all 4 in that folder. Now my Blue screen is converted into Pink one. on my other SD card i put 2.2.1 stock in "dload" folder.
I installed foryo normally by pressing power button and volume keys
I went in pink mode again to copy CWM image.
I went to CWM and installed CM7 (geno) I don't know I tried 10 times to install ezet. It is not at all working with me. anyway But m very happy to be back to CM7 after using ICS MIUI (very much ram hungry).
Thanks everyone for helping me out.
Click to expand...
Click to collapse
will you please give me a backup of this files ?
amss.mbn
boot.img
EMMCBOOT.MBN
recovery.img
thanks .. coz im experiencing blue screen now
I will upload in a few hours. Wait some time
asterisk017 said:
will you please give me a backup of this files ?
amss.mbn
boot.img
EMMCBOOT.MBN
recovery.img
thanks .. coz im experiencing blue screen now
Click to expand...
Click to collapse
http://www68.zippyshare.com/v/67112645/file.html
I have similar issue but can not see the phones storage at all in pink or blue screen, the computer is asking me install drivers for the 'device' when i connect it via usb. I copied dload (official gingerbread) to the external sd card and vol -+ the phone and and the update started to take effect but stopped halfway through 2/2 install. There must be a way to boot/ bring the phone back to life using the external sd card can anyone help me with this?
minor issue as i understand. Try to install 2.2.1 (Foryo).
Are you getting blue screen as of now? or just in boot loop?

No Sound on D801

So I flashed a 4.2.2 ROM, the camera app was bad, (kept rebooting) So I wiped system, flashed again, and the rom (MadhiRom to be exact) worked perfectly. Now, I have no sound at all :/ Any help?
have you tried redoing a clean flash? if so what sound is broken ie just the speakers or the mic or you just cant hear music
Well im not sure if your still looking at this thread or not but using a file explorer (i used root broswer) got to the location seen in the screen shot and place the file i uploaded in that fould it is a stock file this should help with your issue also pls remove the .zip
tbishop91 said:
Well im not sure if your still looking at this thread or not but using a file explorer (i used root broswer) got to the location seen in the screen shot and place the file i uploaded in that fould it is a stock file this should help with your issue also pls remove the .zip
Click to expand...
Click to collapse
well i've a d800 n after flashing cm11 rom all sounds gone i can hear people on call but all they hear from my side is distorion, 2nd tried every kernel out there xcept mehdi as for now the thread is close n i cant share with them. can you help me what was the issue exactly ?

[Q] Installed kernel, phone is f*cked up...

Hey guys,
I've known about this whole modding thingy going on for android phones, and i've decided to give it a shot myself.
I took a backup of everything (copied everything.. didn't use any app for that. not too smart of me..)
Anyway,
I looked around and decided to install Hells Core kernel on my phone, along with Cyanogen Mod.
So after installing the SDK on my computer, unlocking the phone, rooting the phone with SuperSU and Clockwork Mod,
I got to installing the kernel.
I put it on my phone, rebooted into recovery mode, reset all data (dalvik cache and all..)
then I installed the kernel from a zip file I put on the phone, and it all went smoothly.
However, when I reboot my phone - it's all messed up!
The screen is all half yellow, and half is just black - not even text.
In the yellow part, you can hardly tell that it's the first welcome screen - because the text is too big to fit the screen.
Anyway, the whole phone is fk3d up.
I just wanna put it back to the original stock kernel and rom...
How do I do that now?
Thanks a lot guys..
This is urgent >_<
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
jd1639 said:
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
Click to expand...
Click to collapse
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
capzul said:
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
Click to expand...
Click to collapse
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
hassi4042 said:
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
Click to expand...
Click to collapse
Well, I flashed the kernel before I put the ROM, so this happened with HC kernel on stock ROM.
:X
you probably flashed the wrong version of the kernel
You did get the CM Version of Hells Core, right?
This happens to me all the time, just reflash the Roms .zip and you'll be fine.
Sorry to say that, but from your comments it's obvious that you messed up with wrong kernel's version and is not a fault of this specific kernel.
Also the zero kb downloads show bad downloads on your side again.
Sent from my ONDA A9 Core4
capzul said:
Hey guys,
I've known about this whole modding thingy going on for android phones,
Click to expand...
Click to collapse
Lol
Sent from my Nexus 4 using Tapatalk

Any one updated their nexus 4 to 4.4.3 yet? any issues?

So far I found out that if you flash Franco's kernel you will break WiFi. Any other I should know?
Fuzzy Taco said:
So far I found out that if you flash Franco's kernel you will break WiFi. Any other I should know?
Click to expand...
Click to collapse
For now i suggest stick to stock ! or else mod your stock 4.4.3 kernel using Dsixda's Android Kitchen....
or else wait for developers to upload new kernels !
otherwise no issues, performance got a bit low n battery life got better
I just did, via fasboot from Google's image. I don't have a working wi-fi now... Logged on 3G, but then automatic restore starts downloading apps which is not cool on my 3G. Also my N4 is not seen as 8GB, which is not a biggie, has happened before.
Nope, didn't work. Can't figure out why.
So I downloaded the factory image, unzipped it as I always used to, then run the "flash-all.bat" script. And I get this message:
error: cannot open radio-<rest of file name>
The same goes for all files except for the bootloader.
Bootloader is unlocked, was running stock until recently, then used CM for a while, now trying desperately (and in vain) to go back to stock.
Any help would be appreciated. No amount of searching seems to be taking me anywhere.
(Before you ask: I verified MD5 to make sure the file wasn't corrupted; there was no issue on that end.)
kittuboy said:
So I downloaded the factory image, unzipped it as I always used to, then run the "flash-all.bat" script. And I get this message:
error: cannot open radio-<rest of file name>
The same goes for all files except for the bootloader.
Bootloader is unlocked, was running stock until recently, then used CM for a while, now trying desperately (and in vain) to go back to stock.
Any help would be appreciated. No amount of searching seems to be taking me anywhere.
(Before you ask: I verified MD5 to make sure the file wasn't corrupted; there was no issue on that end.)
Click to expand...
Click to collapse
before running the *.bat file, you need to do two things to avoid a complete (including your SDCard) wipe.
1. edit the *.bat file with notepad and then delete the "-w" in the last line. This will prevent a fill wipe.
2. cd into the directory where the factory image and *.bat files are located, THEN run the script - this is why your terminal can't find the files to flash.
Hope this helps.
rickbosch said:
before running the *.bat file, you need to do two things to avoid a complete (including your SDCard) wipe.
1. edit the *.bat file with notepad and then delete the "-w" in the last line. This will prevent a fill wipe.
2. cd into the directory where the factory image and *.bat files are located, THEN run the script - this is why your terminal can't find the files to flash.
Hope this helps.
Click to expand...
Click to collapse
The SD card wipe is the least of my worries I have a full backup, so that's fine. Right now I'm trying to get my phone to boot up fully!
I edited the bat file to reflect the correct path. (Put shortcuts to the original adb and fastboot in the folder with the factory images, replace path in bat file and replace fastboot with "fastboot.lnk")
My strong doubt is that there is some issue with the phone. Will try a toolkit and let you know what happens.
UPDATE:
This is seriously good. I used Wug's NR and some fiddling later, all was well. I still suspect the phone, but ehhh.... 4.4.3. Cheers!
kittuboy said:
The SD card wipe is the least of my worries I have a full backup, so that's fine. Right now I'm trying to get my phone to boot up fully!
I edited the bat file to reflect the correct path. (Put shortcuts to the original adb and fastboot in the folder with the factory images, replace path in bat file and replace fastboot with "fastboot.lnk")
My strong doubt is that there is some issue with the phone. Will try a toolkit and let you know what happens.
Click to expand...
Click to collapse
Cool, but that's a very long way to do it. Just hold shift and right click in the folder where the file is "open command window here" and run the *.bat file. No editing or anything needed.
That's why I never use the bat. Just extract and flash all partitions via fastboot.
Sent from my Nexus 4 using XDA Free mobile app
rickbosch: Er, I should probably explain. My adb and fastboot programs (the entire sdk in fact) are deep inside one drive (the G: drive to be precise. Yes. Stop s******ing.) while the factory image is in the C: drive. So just opening a command prompt in the sdk folder will require me to navigate through to the download folder, and vice versa. So I changed the path in the bat, placed shortcuts in the folder and renamed commands to <command>.lnk. And that was all it took. (It's actually much quicker when done )
oxious119: Fastboot kept bawling that it was unable to flash the radio file. That was why I posted here in the first place. I was eventually forced to use a toolkit (Wug's NRT in case you want to know) and thankfully that solved it for me.
What happened was that I had flashed CM, then I could still go into bootloader and recovery modes. I made the mistake of relocking and unlocking the bootloader. This stopped the phone from booting completely. To make matters worse, for some reason, I was unable to flash the radio (though it was perfectly fine) The toolkit, much as I hate to admit it, did what I could not: it got my phone working. May the heavens praise Wug.
My notification led stop working after flash stock 4.4.3 on my nexus 4. I did a clean install, wiping everything 2 times and no success.
I rollback to 4.4.2 and the led is working again.
My N4 reboots while using camera, did clean flash of factory image an factory reset.
Matr1x kernel issue
Matr1x kernel was the best battery saving kernel I've used. It worked excellent till 4.4.2, but now, after updating to stock 4.4.3, wifi breaks down! Doesn't connect at all! Now running on stock kernel and the battery life has again gone to worse! I wish they'd update soon! Waiting for them to release an update!!!
thawfu said:
Matr1x kernel was the best battery saving kernel I've used. It worked excellent till 4.4.2, but now, after updating to stock 4.4.3, wifi breaks down! Doesn't connect at all! Now running on stock kernel and the battery life has again gone to worse! I wish they'd update soon! Waiting for them to release an update!!!
Click to expand...
Click to collapse
Try THIS, should work for Matr1x too.
Tapatalked from my N4
***Some Problems Still Persist***
I flashed the factory image of 4.4.3 available on Google site on my Nexus 4 and to my huge disappointment the battery drain issue was still there and the phone would shutdown when the battery level would reach below 60%
I was on stock 4.4.2 before I updated.
PS : If anyone out here got a fix to this, please tell me.
I've updated my N4 to 4.4.3, and my Galaxy On Fire 2 HD saves won't load I've baked up them via Titanium Backup PRo, but after restore, when I'm trying to load my game it says "an error occured. please try again later"... and I'm afraid I've lost 30h of gameplay :/
valkyrjur said:
My notification led stop working after flash stock 4.4.3 on my nexus 4. I did a clean install, wiping everything 2 times and no success.
I rollback to 4.4.2 and the led is working again.
Click to expand...
Click to collapse
Working again.
@meatboy371, thank you, thank you, thank you ... It worked ...
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hybrid radio
Anyone know if there's a new hybrid LTE radio for this?
jbounds3 said:
Anyone know if there's a new hybrid LTE radio for this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/ref-mako-hybrid-modem-collection-v2-t2412052
I updated a few days ago and flashed fanco kernel #209 and everything seems to be working good! :laugh:

Battery life & kernel ambasadi rom i9505

I wanted to get imperial kernel v3.3 since they added a google services battery fix
Ran script wiped etc... Phone just stays on model number inital boot screen. :0 This also happened on a stock root rom i tried.
Hybridmax works great but ive got passive battery drain and its a bit outdated. With hulk i cant get wifi working Maybe if tw v2 comes out itll work!? . Kushan seems unstable.
I was hoping imperial would patch the problem yet still no changes :/
any advice?
Try this.
*Update your recovery.
*download the zip again
*flash the file
*clear cache and dalvinks.
*remove the battery and keep it away for 1 min or so.
*place the battery again and turn the phone on
Revert.
DeepankarS said:
Try this.
*Update your recovery.
*download the zip again
*flash the file
*clear cache and dalvinks.
*remove the battery and keep it away for 1 min or so.
*place the battery again and turn the phone on
Revert.
Click to expand...
Click to collapse
I tried your advice before with no results.
Im guessing if trying on a clean install of a different rom had the same problem then the issue lies in a strange place
The other rom was a stock with root :0 so im guessing king of similar to what im running now. Maybe the stock roms have some problems ?
LyQi said:
I tried your advice before with no results.
Im guessing if trying on a clean install of a different rom had the same problem then the issue lies in a strange place
The other rom was a stock with root :0 so im guessing king of similar to what im running now. Maybe the stock roms have some problems ?
Click to expand...
Click to collapse
versions 3.4 resolved the issue i hope my battery life will be as good as everyone says

Categories

Resources