Hello!
I was running a rom (rooted etc.). wanted to do a complete restore to defaults in order to give my phone to someone else. fistly went and erased my sd card from the settings menu. seemed to have done the job (later found out that nothing had been erased). secondly tried to do a system restore to defaults. was waiting and waiting with a message "rebooting". after some time i removed the battery. then went into recovery (s-off) and after wiping everything tried to install a new rom (i had already found out that the sd card was still full therefore i erased everything prior to that). everything seemed to work fine. but. when it booted there weren't any menus etc. tried to reflash rom and tried other roms as well... finally after inserting a sim card as well (was trying without my sim) i got the dialer etc (no initial setup no nothing) i got a menu but settings was missing, market was missing etc. whatever rom i have tried same thing. i can't do anything because settings menu is missing.
any suggestions on how i can fix everything ? (i don't have a nandroid, i know i know, stupid me).
thanking you in advance
Related
Hi,
Im really hoping someone can help me here.
Yesterday my phone threw a wobbly and started to loop boot to the htc logo, it had happened before but i payed little attention. When i removed the battery to reset it i found that it had corrupted my whole sd card, stange file names etc was everywhere.
i decided it was time for a clean start and super wiped the lot then installed arhd,
everything went fine until i went to use bluetooth, nothing i say or do will enable it.
Ive since have wiped and flashed leedroid, arhd, and runny but cant get this little but one of the most used features on my phone to activate.
Ive also reflashed the radio, does it sound like a hard ware failure to you guys?
is there anything that i could have missed, i would also like to add that i havent re installed any previous apps etc and bluetooth still fails to activate.
thanks
sorry to reply to my own thread, but i think i just worked it out. After reading my own post i though about the sd card, i decided to remove the card and reboot, voilia!! the bluetooth is now functioning!!, totally confused now as to why an sd card can affect the running of a seperate piece of hardware!!
ok, it happened again a few time since i posted this thread.
it happened again yesterday and no matter what i done it wouldnt come back.
So i decided to do a nandroid backup and wipe, install a new rom then recover my nandroid backup.
this solved the problem, im not sure what is causing the bluetooth to just die like it does but now i have to keep another rom on my card and a nandroid back up just to get the bluetooth to work- seems strange as the backup is the same drivers etc and stops working. must be hardware...
this dosnt seem to be rom specific as well as its happened now on leedroid, runny, 3dmix, and anotherone i forget the name.
roll on htc edge as im pretty sure i may have a impending hardware failure on the bluetooth radio
So i have just tried to install AOKP 25, whiped everything in AOKP and then installed the rom.
Everything worked fine but then tried to access ROM Control and it crashes instantly.
I have gone back through CWM and whiped again and done another install (3x now) but still the same problem.
So i did a full data erase in settings and the phone resets, brings up the android picture and then after some time boots back in to the phone exactly how it was prior?
Any suggestions as to what is going on?
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
I recently rooted and flashed a recovery on my M8.
I was experimenting with the Fake GPS Free app, and mock locations. Worked great.
But when I turned it off (developer settings, mock location-->None), Actual GPS doesn't work right.
Turned it off, removed mock location setting, deleted app, re-installed app, made sure it was turned off, deleted again.
'High Accuracy' sorta works. It gives an approx position. But using something like google maps navigation gives the message 'Searching for GPS...' and never finds it.
I tried a couple of apps 'GPS Status' and 'GPS Reset Com' which reset A-GPS, but it hasn't worked.
'Device Only' fails completely.
Tried clearing cache.
I even flashed a new ROM (Android Revolution HD (6.0)) but no luck.
I do have a factory reset option - but I'd rather avoid it if possible.
Anyone have any ideas of what else I can try?
Restore the nandroid backup you made (you made one right?) before flashing a new ROM or playing with apps from /system
I actually did not make one. I've just been reading up what it is and what I should have done and now I feel a bit silly.
When it said 'backup your phone' I thought it was just the contents (messages, data, media, etc).
Oops!
It's still all a bit new to me..
Anything else I can try?
Backup your data and sdcard content then flash appropriate RUU, if it's not gonna work it's probably an hardware issue.
I have exactly the same problem with my M8. I tried exactly the same steps and still have the GPS issue. I also restored a previously made backup and did a clean flash of CM13... this couldn't solve the problem.
It can't be a hardware issue
UPDATE: I don't know if it would have worked before, but after reflashing I placed my phone on the ground outside, started GPS Status & Toolbox and waited for a GPS signal. after ~1 minute GPS signal was found and it works fine since then. Maybe I was just too impatient before.
jamesb457 said:
Tried clearing cache.
I even flashed a new ROM (Android Revolution HD (6.0)) but no luck.
I do have a factory reset option - but I'd rather avoid it if possible.
Click to expand...
Click to collapse
Looks like you are new to the modding world. But if you are modding the phone (root, custom ROMs), you should always be prepared to recover from a factory reset (have your data backed up).
And if fact, if you are flashing ROMs without doing a factory reset (within TWRP) you are inviting all sorts of random bugs. In other words, the default wipe in TWRP (data, cache, Dalvik) is always recommended when flashing a new ROM.
So I just tried out some pie roms earlier and when I finally settled on a specific rom, i migrated my files, fixed some settings etc. And when I decided that I was done, I just wanted to transfer some backup files to and from my phone in case I'd need to revert to my prior setup. Weirdly enough, when I pressed the file transfer option on my phone, it would stop or even restart to the bootloader or recovery then I'd have to boot my phone again. I tried it a couple more times and I even lost some data. I then decided to restore a nandroid backup of my oreo rom thinking it was a rom problem but the data partition couldn't be read in bluspark twrp. So, I just did another clean flash of the pie rom (format data, decrypted and all that) and same thing except for the data loss part. Im pretty sure nothing went wrong with flashing as everything works fine on the actual rom but as soon as I select the MTP option, the phone just restarts. Now Im on the said pie rom and everything's working fine but I can't attempt to transfer any files as I'll just run into the same problem. Any help would be appreciated. Thanks!