Database Info

Stuck big time. Help requested (Nexus S)

Hi all,
Well my adventure started last night when I went to return my Nexus S to stock. I did so and it worked well. Then I tried to re-root the device.
After doing so, it now will not boot past the google boot screen (with the unlock icon). It just sits there, even after battery pulls and additional attempts to start up. I can reboot into recovery (fastboot) as shown on the attached images. After hours of reading, it seems I need to flash CWM recovery.img to get the phone to boot. Ok, not a problem. So I installed the android sdk, google and samsung phone drivers and my phone is recognized in device manager.
When I go to flash the recovery.img via fastboot, it just sits there on "waiting on device" and ever goes anywhere. I also have a message on the bottom of the Nexus screen that says "FASTBOOT STATUS - FAILInvalid Command"
I'm at a point where googling is doing no good. Please help.
How can I get my phone to boot? How can I successfully flash the recovery image so I can go forward with root and be done with it?
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.

albundy2010 said:
First step is get fastboot to recognize the phone.
Until the command fastboot devices brings up your serial number you can't flash. Your issue is either you don't got the fastboot driver installed ( does not install correctly by itself on windows 7 64bit) Or your in the wrong directory in fastboot. Or both.
Quides are on the forum how to do everything.
Click to expand...
Click to collapse
Ok, how does one go about doing this on Win7x64?
Quides are on the forum? No idea what that means.

The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.

albundy2010 said:
The forum is the place you're on right now. Read the stickies/how to's or just use the search feature.
Click to expand...
Click to collapse
Believe me, I've done that. Hours and hours worth.
Anyone care to help since apparently this information is so easy to locate? Fastboot simply isn't communicating with my phone and it will not boot past the google boot screen.

After many hours of trying, I figured it out. It had to do with the PDA net drivers. Basically, my phone would not boot up, preventing me from finishing the PDA net install. It kept hanging on "Installing PDA net to your phone" because, well, it couldn't install to my phone (since it was in fast boot mode).
I kept clicking on OK on the dialogue box and it would roll back, uninstalling the PDA net drivers. This was why fast boot could not communicate via cmd.
How I worked around this was by NOT clicking ok, hence not uninstalling the drivers.
It was an epiphany. And a pain in the arse.
So, if you have a similar issue, don't click ok on the dialogue. Leave it in limbo and work your command line magic!

[Completed] softbricked galaxy s4

hey guys, i was trying to domestic unlock an sph-l720 galaxy s4. I followed a lot of different threads here and i felt like I was getting pretty close when i soft bricked my phone. My original modem was the L720VPUGOK3 (running lollipop 5.0.1), i used odin to flash the MDC modem. then (using odin) i rooted my phone. basically i got everything up until i started following this thread:
http://forum.xda-developers.com/showthread.php?t=2530610
which, i got up to step 12) where it tells you to add the lines
ril.sales_code=LOL
ro.csc.sales_code=LOL
then when i tried to reboot, it got to the galaxy s4 screen then went black. usually after that screen it goes to a samsung screen then a sprint screen. I can hook it up to my comp and Odin will recognize it, but no matter what i flash (i've tried re-flashing MDC and root) nothing works. i can also boot it into download mode and recovery mode, i tried doing a factory reset, but that didn't help either. i now no longer have CWM though and so when i go to recovery boot i see this :
android system recovery <3e>
LRX22C.L720VPOGOH1
With the options
reboot now
apply update from ADB
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
enable cp logging
disable cp logging
and i am now lost as to what to do...
update: ok so after about 5 hrs of googling, i have managed to pull my build.prop file. oddly enough i didn't see the two lines i supposedly wrote.
i used build.prop.editor app from google play but i supposed i didn't know what i was doing and didn't actually write them in the first place. so now i'm really lost, since i don't know what my problem is. i'm also having trouble finding a build.prop file to download for cross-reference. any suggestions would be great
update2: ok, after a few more hrs of searching every forum and post i could find, i managed to flash a whole new rom (using odin) onto my s4 with the thought that if i coud just get my phone to reboot, then i could go through the system update over wifi, problem now is that i'm can't turn on wifi. i can press the button but it just goes straight back to off. And since i can't use my sim, i have no way of updating it to my original rom from the phone (which i'm still only guessing is possible). i couldn't find my original rom, so i guess i'll just keep flashing new ones til i find one that works. any suggestions would be appreciated.

Hello and thank you for using XDA Assist,
please post your question here:
Galaxy S 4 Q&A, Help & Troubleshooting
The experts there should be able to help you.
Kind regards and good luck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Trafalgar Square
XDA Assist

adb cant find 4g Adas Mirror, any help pls.

Hi!
This is my first post here, I hope I won't make many mistakes and troubles...
A friend of mine asked me to help him with his car Android based mirror.
The mirror is a "4G Adas Mirror" which is now stucked on the boot screen/logo.
Android version on the device is 8.1.
I've tried to reset through the hard reset button, without success.
I tried to connect the device on my PC to try to get access with adb, no success.
Adb cant see the device, the device list is empty.
When I check in the device manager on my PC I can see under "Portable Devices" installed,
with the name "MTP USB Device".
I also downloaded several drivers but can't install them, not for my device.
And now I'm out of ideas.
If somebody have any idea what could I still try to bring back the device into live, I would really appreciate.
Thank you.
Btw.:
My PC is running win10 x64 Pro

You're probably stuck with only the MTP interface (and not a composite device with MTP and ADB) but it might be worthwhile to double check.
Is the MTP interface active? Can you see any files in Windows File Explorer?
You can check with UsbView.exe to see if there is only one interface, the MTP.
The next step is to try various buttons on boot to see if you can get to recovery, fastboot or ROM bootloader.

Thanks for the fast replay, I cant access the device throug any file manager, as you mentioned, I checked with UsbView.exe already, just to be sure.
The MTP is active.
I've tried many many times the switch combination with the reset button, to try to get into any recovery or whatever cmd line mode, but without success.
The device hase only two buttons:
1. Power button
2. Reset button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Well, there's many ways to skin a cat.
If you open it up there could be a UART with a rooted hardware console.
There could be pushbuttons or test points to get into some other mode.
Good photos will tell us.

So, here we are....
the mirror crashed until I tried to open it.
However, if somebody is interested to hack and poke around this device, I'm familiar to open the device,
make schematics, pictures and try to hack into the device to try to make it alive again.
If somebody is willing to be a part to this pls. let me know and let's get started.

Open it up and take photos.

I'm trying and searching for a way how to open it but not fully crack the mirror, which is actually also a monitor...
I hope I will open the device soo and be back...

[Help] Why does my phone's boot screen look like this?

I got a pixel4a phone, but the startup screen looks like a factory mode screen. how can i remove this screen, thanks a lot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

that's not a lot of info to go by. what did you do prior to getting this screen? since when has this screen been showing? is it rooted? did you do low level stuff with it, and if so, did you do it through a computer or on the phone directly?
the first thing you would want to do is to check if you can enter recovery mode (stock will do if you don't have an aftermarket) and see if you can do something with that, like, say; factory reset.
the next thing you could try is to first backup your flash, and I mean from sector 0 to EOF, and a second backup per partition, then flash a stock rom you could get online.
I WOULD preffer to just diagnose the problem and fix it non-destructively but phones and their OSes are not built to accomodate repair beyond changing the screen/batery and resetting/flasing the ROM
P.S. throw in the chipset type while you're at it I.E. MTK or QLM

Thank you for your response, bro! This phone is a second-hand phone. When I received it, it only had the factory mode. I flashed Android 11 through the website flash.android.com, but every time I boot up the phone, the screen will display for a few seconds before entering the system. I searched online and it seems that the phone is still in factory mode and needs to be activated to normal mode, but I haven't found a way to switch to normal mode.

1. Enable ADB ( AKA USB Debugging ) on phone
2. Connect computer and phone via USB-cable
3. On computer run ADB command
Code:
adb reboot

oldmaize said:
Thank you for your response, bro! This phone is a second-hand phone. When I received it, it only had the factory mode. I flashed Android 11 through the website flash.android.com, but every time I boot up the phone, the screen will display for a few seconds before entering the system. I searched online and it seems that the phone is still in factory mode and needs to be activated to normal mode, but I haven't found a way to switch to normal mode.
Click to expand...
Click to collapse
well, taht just sounds like the ROM didn't come with a boot animation/logo so I suggest if you want one you can well... there's not much you can do without tripping tamper triggers I.E. install rootkit & modify system partition (can't be done post pie) or unpack system image, insert the animation/logo and repack, but then you have an orange state device and that's not much better than that factory logo, or you lock it without image verification enabled and hope that something doesn't rely on it
android isn't built to be moded, so you have to mod it before building an hoo boy is that a wild ride
P.S. on second read, the ROM might be in eng mode instead of userdebug or user
you could check it by either terminal emulator, issueing the command `getprop` and search for build variant or do so through adb

Phone Freezes and Reboots a minute after starting

Hey everyone,
A few days ago I was taking the battery out of my phone, to get to the SD card, without shutting it down properly first, which presumably broke some component in my system. When I booted the phone back up again, I was noticing some weird behavior: I am able to use the phone normally, but after about a minute, the whole phone freezes and I am not able to interact (touch or power / volume buttons) with it in any way anymore. After the phone has been frozen for about a minute, it will crash and restart and I will be thrown back into the boot sequence.
Luckily I discovered, that the Safe Mode worked fine and none of these problems ever occurred there. I am able to make phone calls and access the internet via the default browser just fine there.
When using adb to get the log below, I noticed I was still able to use the shell (cd, ls, etc.) after the display froze, so I assume only some of the system is having problems.
Phone: Fairphone 3
OS: Lineage 20.0 with MindTheGapps. I updated to 20.0 a few weeks ago and already tried OTA updating to the newest version after the phone started misbehaving, without any luck.
My phone is/was rooted using magisk, but I already uninstalled it trying to prevent the crash.
Below I added the output of adb logcat, which I ran as soon as the connection to the PC was established and until I saw the bool logo again.
One thing I noticed was the message
[ 06-20 00:07:09.165 1179: 9685 E/qdmetadata ]
Unknown paramType 4096
which was issued 4000+ times during the duration the log was taken. I don't know about the fatality of this error, but digging in the lineage Source-Code I think it relates to the display.
I already thought about resetting the phone to factory default, but I have a lot of stuff on there and would prefer to not do so, ignoring the fact that this might not even solve the problem, depending on how deep it lies.
Thanks in advance,
~Okaghana

That's what ChatGPT says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I already uninstalled all apps that I recently installed and even some older ones I didn't need.
One more thing I noticed: When my phone has low battery power (below 10%) it takes longer to freeze. I suspect a background activity is the culprit and when the phone is low on battery the power saver increases the time until it is executed

Okaghana said:
I already uninstalled all apps that I recently installed and even some older ones I didn't need.
One more thing I noticed: When my phone has low battery power (below 10%) it takes longer to freeze. I suspect a background activity is the culprit and when the phone is low on battery the power saver increases the time until it is executed
Click to expand...
Click to collapse
Do you have custom recovery ? To reflash the system, I think the update crashed the system.

Originally I had the Recovery that came with LineageOS, but I patched it for Magisk. I flashed the original, unmodified LineageOS Recovery, but that did not fix it :/

Okaghana said:
Originally I had the Recovery that came with LineageOS, but I patched it for Magisk. I flashed the original, unmodified LineageOS Recovery, but that did not fix it :/
Click to expand...
Click to collapse
What was your original os of the phone

The original OS is Fairphone OS

Okaghana said:
The original OS is Fairphone OS
Click to expand...
Click to collapse
Well my friend it's time for you try to trick your phone with firmware upgrade and return to the original os I suppose, but you said you have files one the phone am not sure about that but you can still flash twrp to backup, tell me what you think