Database Users

[HELP] Root Problem

Hi,
I rooted my Nexus S but somewhere around got lost and panic. So don't have any backup. Will try to explain everything in order to see if anyone can help me.
Followed this h**p://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/ guide and did everything. was going well. But after the bootroot step things got messy. Now I can only enter recovery mode, and even upload ROM's. But none of the Back, Search or Home key on the phone work. Even tried to install Stock Google 2.3.3 but it doesn't install at all. Anyone can say if it was the Bootrood and how I can revert. Or is my Nexus S bricked...
Thanks and sorry for the bad english.
R.

For hacking Nexus S, I would suggest doing it from the Android Development forums for Nexus S rather than a website. And Recovery, you aren't supposed to be using Back, Search, Home key.. its the volume buttons and power button.
What Recovery are you using? Clockwork or Stock?

using clockwork. the buttons don't work after. when i install any rom. after. and the stock roms just don't install.
Bootloaderversion - I9020XXkA3
Baseband Version - I9020XXKB3

choclacte said:
using clockwork. the buttons don't work after. when i install any rom. after. and the stock roms just don't install.
Click to expand...
Click to collapse
what are the steps you are using to flash a ROM? just asking to see if you're doing it properly. list what ROM, and Clockwork 3.0.0.5 correct?

Tried already CyanogenMod7 Nightly #12, Axura-1110-NSE, GingerS-ROM-v0.7-signed and the GRI40 2.3.3 (stock).
Yes, my ClockworkMod is v3.0.0.5.
I manage to install the rom's, but the problem is after. Looks like the screen isn't calibrated. And none of the Home,Search,Back and Options 'keys' work. Just power, and the volume. but if the phone enters in standby mode I can't get him back. Any way to just put it like factory again. In other words, is it possible to 'Unroot' or just get the stock working?

choclacte said:
Tried already CyanogenMod7 Nightly #12, Axura-1110-NSE, GingerS-ROM-v0.7-signed and the GRI40 2.3.3 (stock).
Yes, my ClockworkMod is v3.0.0.5.
I manage to install the rom's, but the problem is after. Looks like the screen isn't calibrated. And none of the Home,Search,Back and Options 'keys' work. Just power, and the volume. but if the phone enters in standby mode I can't get him back. Any way to just put it like factory again. In other words, is it possible to 'Unroot' or just get the stock working?
Click to expand...
Click to collapse
Screen not being calliberated is a 2.3.3 problem with yellowish tint. To fix this you need a kernel supporting Voodoo Color. And yes, download a nandriod backup and restore it. You can find the backups on the Dev forum.

already wiped everything from the phone.
the problem is that none of the keys after work.

choclacte said:
already wiped everything from the phone.
the problem is that none of the keys after work.
Click to expand...
Click to collapse
Wiped Dalvik / Cache / Data? Try downloading a nandroid backup from the dev forums then Nandroid Restore, and for a LAST RESORT. you can try Odin but I never used it for the NS.
If not then, you seriously messed up your phone by doing improper instructions on that website (or. the website did it wrong)

zephiK said:
Wiped Dalvik / Cache / Data?
Click to expand...
Click to collapse
How to do this on windows7 or Mac?
already did that. wipe all the cache and data. everytime i try to install a rom need to do that.
how to do Nandroid restore.

Problem solved.. still don't know how.. but it seems to be working. Many thanks!

nandroid restore: download one.. put it in clockworkmod/backup
then go into backup/restore in recovery
dalvik wipe is in advanced in recovery

[Q] Droid X stuck on M logo

I recently got the rooted gingerbread update to my X well thought it would be sweet to get a rom for it. Tried to install it well went through fine, but when I tried to reboot it got stuck on the M logo and tried wiping data and cache, yet nothing seems to fix it. Any help would be great not used to the X as my main phone is the TB.
(also sorry I did checking of how to fix but didn't quite follow how to use I see I need rsdlite and full VRZ_MB810_2.3.34_1FF_01.sbf is there any other files I will be needing?)
While reading RSD lite is windows ran correct?

So im kind of in the same boat you are. I am unable to flash liberty 1.5 because it gets stuck on the boot screen.
First off can you get into recovery?
If yes did you back up your original rom before trying to flash the new one?
If yes the best way I found to flash a backup is to do: wipe data/factory reset, wipe catch partition, then under mounts and storage format: system, data, catch. Then try installing your backup.
If you have no for any of these tell me and I might know a way around them. Like I said im in the same boat and have dealt with some of the stuff your experiencing.

BrownEye02 said:
So im kind of in the same boat you are. I am unable to flash liberty 1.5 because it gets stuck on the boot screen.
First off can you get into recovery?
If yes did you back up your original rom before trying to flash the new one?
If yes the best way I found to flash a backup is to do: wipe data/factory reset, wipe catch partition, then under mounts and storage format: system, data, catch. Then try installing your backup.
If you have no for any of these tell me and I might know a way around them. Like I said im in the same boat and have dealt with some of the stuff your experiencing.
Click to expand...
Click to collapse
Unfortunately I cant get into the recovery it seems to be broken I can only get into the stock bootloader I believe the blue one where you can update clear cache and wipe data. Wish I could get into recovery would be cake walk then.

Sounds like you both need to sbf. There are stickies at the top of this forum with instructions for Windows and Linux.

If you intend to flash a froyo rom after installing the GB update, you have to SBF back to stock first.
Sent from my DROIDX using XDA Premium App

atrix non responsive after cm7

I was running cm7 since it was first released. I got a new phone so i decided to give my atrix to my younger brother. The problem is after i went through the process of putting the phone back to stock, there now seems to be dead zones on the phone. For example i cannot press the w,e,s, keys. Can anyone help me or tell me if i've done something wrong?

I'm not sure you did anything wrong specifically. Did you make sure the clear all the cache? How did you put stock back on it (IE. flashed stock via CWM, moto fastboot, etc)?.

Boot into recovery, wipe dalvik cache, system cache, reflash your firmware of choice, reboot.
Sent from my MB860 using Tapatalk

Ive had numerous problems with cm7 for atrix but ive found that backup everything you need with titanium backup and then just reflash the rom and wipe the data and davlik cache and it should. But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Sam

samdrake112 said:
But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Click to expand...
Click to collapse
The CM7 beta does not have the issues that the OP described so please don't let him think that's the reason.
OP, re-flash your phone with a different ROM or with CM7 again and see if it still persists.

Help needed. System ui has crashed

help! i install the newest cm nightly (20130704). after flashing and rebooting, i got an endless loop of 'system ui' has stopped.
i tried factory reset and reflash. didnt work.
what can i do now?? it seems that my computer cannot detect my n4,
i have twrp custom recovery if it helps.
i really need help guys, i cant live without my phone.
i promise ill do nandroid backups next time ((

icemilo69 said:
help! i install the newest cm nightly (20130704). after flashing and rebooting, i got an endless loop of 'system ui' has stopped.
i tried factory reset and reflash. didnt work.
what can i do now?? it seems that my computer cannot detect my n4,
i have twrp custom recovery if it helps.
i really need help guys, i cant live without my phone.
i promise ill do nandroid backups next time ((
Click to expand...
Click to collapse
Seems like its a known issue in the latest nightly. Youll need to revert back to yesterdays. Read this

icemilo69 said:
help! i install the newest cm nightly (20130704). after flashing and rebooting, i got an endless loop of 'system ui' has stopped.
i tried factory reset and reflash. didnt work.
what can i do now?? it seems that my computer cannot detect my n4,
i have twrp custom recovery if it helps.
i really need help guys, i cant live without my phone.
i promise ill do nandroid backups next time ((
Click to expand...
Click to collapse
reflash the last working rom. if you dont have it in your storage, youll have to push it to your phone over adb via your recoverys adb push option.

chromium96 said:
Seems like its a known issue in the latest nightly. Youll need to revert back to yesterdays. Read this
Click to expand...
Click to collapse
thanks a million man

Soft-bricked Nexus 4, no guide will work

My Nexus 4 had been running Cyanogenmod (cm-12.1-20151007-SNAPSHOT-YOG4PAO334-mako) correctly for months. Two days ago, the screen failed to auto-rotate when I tilted the phone so I decided to reboot and see if that worked. Not only did it not work, the device went into a bootloop. It would boot, ask for my encryption password, accept the password but the OS would never start (I waited over 2 hours).
I'm able to use adb, fastboot, and access TWRP.
I tried reflashing CM12 to no avail. I've also tried going back to stock by reformatting all partitions in fastboot and flashing stock bootloader, radio, and system image (also in fastboot). That's where I'm at right now. I have everything stock except for the recovery partition where I have TWRP.
Here's the TWRP log: http://pastebin.com/MCKD73G0
Here's the dmesg log: http://pastebin.com/BdVjV2vz
Here's the last kernel message log: http://pastebin.com/DBQQBFQv
Any ideas?

I have a very strong hunch that this problem has got something to do with the sensors.
I flashed Android 4.2.2 and, to my surprise, the phone booted correctly into Android. No other ROM (stock or otherwise) would boot correctly. As I mentioned in the OP, screen auto-rotation isn't working so I downloaded an app to test other sensors. The proximity sensor, pressure sensor, light sensor, and the gyroscope don't work. I strongly doubt this is a software issue but I'm not ruling it out yet. I will try to open the phone case later tonight and move the sensor around, it might be stuck.

Just had a pro take a look at my phone. He said there's nothing wrong with the sensors so it must be a software problem. I've been trying to fix this for days now.
Any ideas would be greatly appreciated.

I just noticed that my phone does not have the /sys/class/sensors/ or /sys/devices/virtual/sensors/ folders, is this normal? If not, how can I solve this?

Feareilo said:
I just noticed that my phone does not have the /sys/class/sensors/ or /sys/devices/virtual/sensors/ folders, is this normal? If not, how can I solve this?
Click to expand...
Click to collapse
I had this issue twice.. flashing an old version of Frank ROM (in L preview times).. all my sensors got screwed... and trying to flash other roms or factory resetting the phone didn't work!
So I downloaded latest factory image and flashed it with the flashall.bat script
Voilà! All the sensors started to work again!! And they still work! So... some very deep part of the system can be wiped only by the stock recovery factory reset.. I don't know why though.. but that's it!

bart.found said:
I had this issue twice.. flashing an old version of Frank ROM (in L preview times).. all my sensors got screwed... and trying to flash other roms or factory resetting the phone didn't work!
So I downloaded latest factory image and flashed it with the flashall.bat script
Voilà! All the sensors started to work again!! And they still work! So... some very deep part of the system can be wiped only by the stock recovery factory reset.. I don't know why though.. but that's it!
Click to expand...
Click to collapse
Thanks for your input. Unfortunately, that didn't work. Flashing stock ROMs didn't work and neither did doing the factory reset.

Feareilo said:
Thanks for your input. Unfortunately, that didn't work. Flashing stock ROMs didn't work and neither did doing the factory reset.
Click to expand...
Click to collapse
Sad to hear that... did you already factory reset from the stock recovery?

bart.found said:
Sad to hear that... did you already factory reset from the stock recovery?
Click to expand...
Click to collapse
Yeah