hello everyone,
I bought a Nexus s from a friend of mine
it had a little problem of multiple rebooting.I though I will flash it and everything will be okay.It didn't go that way.
Specification:-
Nexus S
Fastboot Mode
Product name - HERRING
HW Version - REV 52
Bootloader Version - 19020XXL1
BaseBand Version - 19020XXL1
Carrier info - EUR
this is what it says in bootloader
Problem:-
My new Nexus s reboots just in middle of nothing.(I'll explain what i mean here)
Q:-while it get rebooted what activity caused reboot
A:- it happens in number of occation
*sometimes I open market(play google now) browse some app and click on install button-rebooted
*sometimes I put mobile on chargin and open call log - rebooted
*sometime I open camera to click pic - rebooted
* sometimes I click on message - rebooted
*sometimes I just unlock the screen lock and rebooted
*most irritating - someone calling me it gets rebooted and the callers number dosent even save in call log
basically there is no pattern for rebooting
* sometimes even it just idle and getting charged it multiple times reboot itself
-and this happens several times a day
this problem was reported on many places before me
system didnt allowed me to post outside links where it was reported
and google has released fix for that as read somewhere where it was reported this bug in android 2.3.4 (atleast they said like that),
Solution I tried :-
downloaded stock rom where the uploader said it works fine and has no reboot issue it was android 2.3.6. so i assumed that reboot issue should not bother anymore
before installing Stock rom I followed guide to root on nexusshack.com and I did not forget to wipe all data/factory reset, wipe dalvik cache,battery status
still problem exist
then I tried new ICS consider there will be no chance for this error
but again I failed to fix the reboot error
here is specification of Roms I tried, I used each of these ROM for more than 3 days,just to be ensure, that problem still persist
ICS 4.0.3 -
Baseband version - 19023XXKI1
Kernel Version - 3.0.8-gb55e9ac
[email protected]#1
Build number - IML74K
Android 2.3.6
Stock rom I tried -3 different stock rom download from different sites having same specification
Baseband version - 19023XXKF1
Kernel Version - 2.6.35.7-gf5f63ef
[email protected]#1
Build number - GRK39F
after this didnt worked I tried changing kernel...thinking that may fix this problem
I dont know how this could fix the problem ..but I was so desperate to fix it, I just give it a go,as I was and I am ready to do anything which is possible to do to fix it,
Kernel I tried-
netarchy-1.3.7-bfs-2.3.4-signed
netarchy-1.3.7-cfs-2.3.4-signed
netarchy-1.3.7-bfs-2.3.4-universal-signed
I will be very glad if any expert give me advice to what else I should do?
or this problem is due to faulty board and I have to pay to replace it?
I'm totally confused
can someone please help me out solving my problem, if it can be fixed
P.S:- for those who get angry and reply in tone everything works good on my nexus there is no such problem exist when someone says my nexus has reboot problem (saw this happening on many places where the bug was reported).I'm glad that your device works without problem, unluckly my device dosent, and I want to fix it, will be nice if you guys will be co-operative,rather than just mocking and spamming
Thanks in Advance
-Shree
reserved
Reserved in case needed
Try data/factory reset, format /system and format /boot. Now try flashing a Stock ROM. If this doesn't help it is probably a hardware issue and needs the SoC replaced.
Harbb said:
Try data/factory reset, format /system and format /boot. Now try flashing a Stock ROM. If this doesn't help it is probably a hardware issue and needs the SoC replaced.
Click to expand...
Click to collapse
I'm not very much expert in these things...
from the above things what I know is factory reset..
will he very nice if you provide a link to guide describing how to,
format / system and format /boot.
You have to go into recovery and you'll notice the options
Sent from my Nexus S 4G using xda premium
Recovery --> Mounts and Storage --> Format /system, Format /boot
Thanx a lot.....
I did format system,boot,cache,data,
then wiped fata/ factory reset,dalvik cache,cache partition,battery status (all wipe option)
now installed a stock rom.
I'll try this for couple more days....and see if problem still exist
if it still exist....that is for sure its hardware problem...and first I'll have to detect which hardware is faulty, causing the problem..hope I dont have to do that
Thanx a lot guys
I tried it the way you said it,
the problem still exist...but the reboot amount frequency is reduced...not it reboots just 2-3 times a day
Related
Hey, so as stated in the title, I have recently flashed Cyanogenmod7. Initially, version 7.2.0 and then the nightly build released on 10/7/12. I can no longer receive mobile data. I realize this is a very common problem and have searched through multiple forum posts here and elsewhere online. I also flashed a new kernel in an attempt to fix it (not sure of the name, found here: http://forum.xda-developers.com/showthread.php?t=1073626).
Mobile data will appear (and work) for the first 10-15 seconds after startup if wifi is disabled but then vanishes afterwards. I have tried changing the mobile network settings and apn settings in a number of ways but no method ever works (most of the ones found online appear to be at least a year old so perhaps I just need more modern entries). Any help would be greatly appreciated.
viveksmother said:
Hey, so as stated in the title, I have recently flashed Cyanogenmod7. Initially, version 7.2.0 and then the nightly build released on 10/7/12. I can no longer receive mobile data. I realize this is a very common problem and have searched through multiple forum posts here and elsewhere online. I also flashed a new kernel in an attempt to fix it (not sure of the name, found here: http://forum.xda-developers.com/showthread.php?t=1073626).
Mobile data will appear (and work) for the first 10-15 seconds after startup if wifi is disabled but then vanishes afterwards. I have tried changing the mobile network settings and apn settings in a number of ways but no method ever works (most of the ones found online appear to be at least a year old so perhaps I just need more modern entries). Any help would be greatly appreciated.
Click to expand...
Click to collapse
The CM team has yet to fix this, and I doubt it ever will be fixed. It's present on all AOSP based ROMS. I guess if they set the modem to reset on bootup, it could fix it, but I have no idea how to do that.
FatalityBoyZahy said:
The CM team has yet to fix this, and I doubt it ever will be fixed. It's present on all AOSP based ROMS. I guess if they set the modem to reset on bootup, it could fix it, but I have no idea how to do that.
Click to expand...
Click to collapse
So, to get my data back should I just reflash stock?
Have you tried hard resets? Holding power and volume up until the phone reboots?
buru898 said:
Have you tried hard resets? Holding power and volume up until the phone reboots?
Click to expand...
Click to collapse
Yeah, I've tried that. Still nothing.
I am using cm7 no problem with data whatsoever you shoud try wiping cache and dalvik cache and after that fix permissions and if u wanna install a custom kernel thats what i do when i flash a rom and works fine
Sent from my LG-P999 using xda app-developers app
ted619 said:
I am using cm7 no problem with data whatsoever you shoud try wiping cache and dalvik cache and after that fix permissions and if u wanna install a custom kernel thats what i do when i flash a rom and works fine
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
I've also tried wiping the cache and dalvik cache with no effect. I have also installed a custom kernel with no effect. I am not entirely sure what you mean by fixing permissions.
Edit: searched and figured it out. Tried fixing permissions in combination with the other two options. Still no effect.
Sorry to bump an old topic but I accidentally reflashed Cyanogen (pressed wrong zip in recovery) and now it's working so if anyone else has this problem, try doing a factory reset and then reflashing old data.
Incompatible*with*other applications(s) using the same shared user data
ave just installed Official JB Rom from sam mobile singapore version...
now downloading maps from playstore and get this error...
Anybody know how to fix?
Error fixed by factory reset and reinstall new samsung account.
maybe it updated from my old rom and kept or corrupted some files caused problems?.
anyway if anyone gets this problem a factory reset will fix it..
MRBR7 said:
Error fixed by factory reset and reinstall new samsung account.
maybe it updated from my old rom and kept or corrupted some files caused problems?.
anyway if anyone gets this problem a factory reset will fix it..
Click to expand...
Click to collapse
+1
after spending quite a few hours following "tips" and directions from various sources, factory reset was the only one that resolved the incompatible <blah> shared user id issue!!
I think my issues were when i flashed the JB rom with mobile odin..
First i was on PA3.5 and it wouldnt work for some reason although at the time i was very tired as waiting a very long time to download the rom with slow speeds so maybe i did something wrong?.decided to flash recovery back to earlier version of Skyhigh Rom that was working ok then from here i installed the new stock rom over the top with mobile odin.It booted up and gave the android is updating screen.then loaded up with my custom launcher from the skyhigh rom.I thought this was funny as really should have wiped everything.I didnt even get the language change screen or set up its like it kept my old settings from skyhigh.Its as though it updated it and kept everything similar to an OTA update.as posted had the problems with Maps But then factory reset fixed it and wiped it clean again.This time i got the Laungauge screen on start up and the new stock lock/home screens..
Updated to v9 today...after receiving a call (did vibrate), I found that all kinds of vibration stopped working, even in recovery mode.
I googled it and find https://forums.oneplus.net/threads/vibration-suddenly-not-working.76462/page-2 that someone else is having the same problem with franco. I am so frustrated as it seems that only full reflash can fix the problem.
Anyone has others solution on it?
ROM: Stock CM 11S
Kernel: franco.Kernel v9
I did change according to http://forum.xda-developers.com/showpost.php?p=54571945&postcount=271 today. Not sure if it relates to the issue.
PS Don't have the permission to ask in franco thread so I better post it here...
Solved:
My solution is to accidentally drop the phone on the ground and make a scratch on the silver edge. And the vibration is back. It is a hardware problem. But maybe it is triggered by a software issue...
knzzz said:
Updated to v9 today...after receiving a call (did vibrate), I found that all kinds of vibration stopped working, even in recovery mode.
I googled it and find https://forums.oneplus.net/threads/vibration-suddenly-not-working.76462/page-2 that someone else is having the same problem with franco. I am so frustrated as it seems that only full reflash can fix the problem.
Anyone has others solution on it?
ROM: Stock CM 11S
Kernel: franco.Kernel v9
I did change according to http://forum.xda-developers.com/showpost.php?p=54571945&postcount=271 today. Not sure if it relates to the issue.
PS Don't have the permission to ask in franco thread so I better post it here...
Click to expand...
Click to collapse
I have has problems with vibrations too, It worked in recovery but not in Cm 11s, I installed Pacman rom and now it works, also works with Franco kernel but use aosp.
Try updating to r10 and see if the problem still occurs.
Sent from my One using Tapatalk
I am on r10 now but still no vibration in any circumstances...I have once restored the vibration after many trials of wipe (in recovery mode) and reflash but when I signed in my google account with "backup & restore" box checked, it lost again. So i think it should be a software problem. Unfortunately I couldn't restore the vibration again as I forgot my actual steps at that time.
I will try flashing asop when I am free. Thanks.
knzzz said:
I am on r10 now but still no vibration in any circumstances...I have once restored the vibration after many trials of wipe (in recovery mode) and reflash but when I signed in my google account with "backup & restore" box checked, it lost again. So i think it should be a software problem. Unfortunately I couldn't restore the vibration again as I forgot my actual steps at that time.
I will try flashing asop when I am free. Thanks.
Click to expand...
Click to collapse
How many other kernels have you tried as well for troubleshooting purposes?
playya said:
How many other kernels have you tried as well for troubleshooting purposes?
Click to expand...
Click to collapse
I just tried stock. I used to think to fix the problem I can only wipe everything and do full reflash via fastboot posted in OP. However I just can't format 'userdata' as I mentioned in my other post http://forum.xda-developers.com/oneplus-one/help/help-fail-to-wipe-using-fastboot-t2839512.
Again I will try to flash another kernel to see if it works. Thanks.
knzzz said:
I just tried stock. I used to think to fix the problem I can only wipe everything and do full reflash via fastboot posted in OP. However I just can't format 'userdata' as I mentioned in my other post http://forum.xda-developers.com/oneplus-one/help/help-fail-to-wipe-using-fastboot-t2839512.
Again I will try to flash another kernel to see if it works. Thanks.
Click to expand...
Click to collapse
That's a lot to do to try and fix issue. I would restore my nandroid that was working prior to flashing kernel and flash another kernel for testing.
Solved!!!
My solution is to accidentally drop the phone on the ground and make a scratch on the silver edge. And the vibration is back. I should thank the maid who bumped into me.
So I am wrong it is a hardware problem. But maybe it is becoz the vibration strength was low and somehow break the vibrator.
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
Hey all,
i have a Bigproblem. =(
I bought a new Honor 6x and unlocked the Bootloader. Then i installed TWRP successfully.
After that downloaded the RR 5.74 and OpenGapps and installed them, too.
NOW after restarting the Honor 6x, the phone wanst me to enter a Android PIN/Password.
I cant do anything...i have to enter a Android Pin.
Before installing i didnt enter any Passwords and i deactivated the Fingerprint.
Do you know what i should do?
I dont know what to do know =((
I tried my unlock code, my SIM Pin etc but everytime it says "Falsches Passwort" - Wrong Parrword.
Also i tried to format via Twrp but it says "Unable to format to remove encryption."
Please help me...
Try this , go to TWRP and the wipe data and click advanced , then select data , cache and dalvik cache, this might help .
NOTE : this may erase all the data of your phone including contacts pics etc
asked for password after flashing LineageOs ROM
Hi Folks,
this is my first post in this forum and I'm completely new to whole Android stuff, although I'm a well experienced Gentoo user.
I have nearly the same trouble, except the before mentioned message "Unable to format to remove encryption."
After flashing the latest ROM (lineage-13.0-20170205-UNOFFICIAL-berlin.zip) I also got asked for a password I didn't have.
I tried different ways of wiping cache, dalvik-cache, data, system, trying factory reset and also formatting /data and but nothing works for me.
Of course I can go back to my latest working Backup of Marchmallow 6.1, but I wont get rid of all that google stuff, so your help to my upgrade path to LineageOS is very much appreciated.
In the meantime I also tried to flash lineage-13.0-20170203-UNOFFICIAL-berlin.zip and later also the Resurrection Remix 5.7.4 for Honor 6X (Berlin), but after every first start of theses custom ROMs, a password request came up.
I definitely deleted my fingerprints before and at last I additionally deactivate my SIM Password.
What could be the root cause for this?
One stupid question more, please. What for is the recovery.img here needed:
https://forum.xda-developers.com/devdb/project/?id=19229#downloads
If it means only the TWRP.img file, I'm using twrp-3.1.0-0-berlin.img which should be correct.
Also I installed supersu SuperSU-v2.79-201612051815.zip out of twrp, cause it missed the often mentioned direct root option within advanced options. I guess it was part of earlier versions of twrp, right.
Have I overlooked some important step?
Best regards, Andy.
Honor 6X = Berlin or not?
Cause the twrp devices site has only one entry for the Honor 6X (as of today)
and the call its code name Berlin, I (or we) came to this possibly wrong conclusion, I have exact this version.
But now I guess I'm wrong, cause my device is a
BLN-L21C432B130
which is mostly called in this forum as a BLN-L21 : Europe, Netherlands, Italy Variant.
Am I right, that the linageos and the RR versions I (or we) tried to flash, are wrong versions for such devices, and the right ones doesn't exist until now?
Andreas, what's your exact Build Number? Did you the same fault as I do?
Could anyone of the more experienced member please state that.
Best, Andy.
Pin furthermore needed
Sorry Folks,
as a new member, I have not enough rights to post directly to the ROM section here:
https://forum.xda-developers.com/honor-6x/development/rom-resurrection-remix-m-5-7-4-berlin-t3551705/page5
A member called Pokhara solved the PIN issue, but I can't do so and asking myself what I'm doing different or wrong. I tried it several times inspiered by his and different posts, but equal if I'm flashing RR 5.74 or LineageOS, after a restart I'm asking for a PIN.
Possible you'll see what I'm doing wrong or differently, compared to your successfully installation:
At first, I'm deleting all my Fingerprints and deactivate the using of it into the Phone Settings.
I'm using latest TWRP-3.1.0-0 (berlin. image)
Using its Advanced Wipe function, wiping the following partions / directories:
Dalvik / ART Cache
Cache
Data
Internal Storage
System
(but of course not the Micro SDCard)
Question: is it right to exclude the Boot Partion, which is not listed here. I guess cause it is not checked into the settings dialog as wipeable.
I'm afraid that would brick my phone (prevents booting it) - right? (Or is this the difference to your procedure)?
Than I'm flashing RR and than the recommend GApps package too
or, on a different trial the LinageOS.zip alternatively.
Reboot, Splash screen of RR or Linage appears, asking for the PIN which I can't skip > finished
Any help is very much appreciated.
Best regards, Andy.
Password problem solved!
Good news from my side, folks.
Yesterday I've got solved my problem and I'm wondered a little why none could give me the right hint before....
After using the older version of twrp-3.0.2-0 for the first time, everything works like a charm.
For me the misleading description was, to not name the version and what this file contains (recovery.img) here:
https://forum.xda-developers.com/devdb/project/?id=19229#downloads
so please rename it to something like: twrp-3.0.2-0-berlin.img
This prevents other users (like me), to use a newer version, which was also recommended for this phone (cause more bugs are fixed), but this had never worked for me successful with this phone!
I presume: If you're not using a newer version of EMUI 4.1 or a BuildNo. BLN-L21C432B130, or Android 6.x.
Nevertheless, now I'm able to install LinageOS or RR 5.7.4 successfully. So I hope this conclusion could also help some others out there.