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
Related
Hello to everyone.
I have phone LG g pro 2 D838 made in Korea, that has strange symptoms. When it boots, appear screen with keyboard and input box with text ''Enter PIN/password to decrypt 30/30 attempts remaining". After I entered some code, it shows "29/30 attempts remaining, and no matter how many times wrong code is entered, still remains 29/30. Download mode working, and I try to flash latest stock rom 10f, but nothing happened. Then I try stock roms 10a, 10b and 10d, but still nothing. Next to the download mode, I have a recovery mode, in which there is no menu. In this mode, it is possible to access phone with ADB, but everything is read only, and system is not mounted. I can list folder contents, but I can't push or pull, and when i try to use shell, I get a message " -exec '/system/bin/sh' failed: No such file or directory", because system partition is not mounted. ADB Remount generate error " remount failed: Success ". I forgot to mention that every time when i try to flash stock rom, in box on phone display was written, in red letters, 'ROOTED'. I guess that unroot is not succeeded . Also suppose that possible solution is to flash some custom rom with recovery, but i can do that only if I have it in KDZ format. Does anyone know how to make a custom rom in KDZ format, or someone already has it? Does anyone know some other solution?
{
"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"
}
Thanks in advance
From what it looks like, you've encrypted your phone. That explains the password on startup and the unmounted system.
If you don't know your encryption password, you have a bit of a problem on your hands.
From what I know, there's no way to hack into or change your phone when it's encrypted.
Turtle_Cookies said:
From what it looks like, you've encrypted your phone. That explains the password on startup and the unmounted system.
If you don't know your encryption password, you have a bit of a problem on your hands.
From what I know, there's no way to hack into or change your phone when it's encrypted.
Click to expand...
Click to collapse
In first, thank you on reply ,Turtle_Cookies.
If the phone is encrypted, it should be possible to reset it to factory settings. The user data is encrypted, so it would delete them and set to the default settings, and that should recover the phone. On the other hand, I can access to certain directories by ADB (like etc,sys), but can't change it. Am I right?
Same Issue
Did you found solution to this?
I have a Samsung phone model GT-i9060 with Android 4.4 and suddenly one day phone suddenly switched off and refused to start.
On powering on it would get stuck to this battery animation screen:
{
"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"
}
On holding the Power+VolDwn+HomeKey I get this Warning screen with two options to continue to recovery (VolUp) or reboot
and selecting either of those options leads to these following screens: recover mode boot screen
But nothing happens then, It switches off again after 5-10 seconds on both the screens and I tried
Code:
adb devices
during all those stages but phone is not detected on PC
I need to recover some critical data from this phone which is paramount. Can someone guide me as how should i proceed with data recovery or extraction?
Asvthama said:
I have a Samsung phone model GT-i9060 with Android 4.4 and suddenly one day phone suddenly switched off and refused to start.
On powering on it would get stuck to this battery animation screen:
On holding the Power+VolDwn+HomeKey I get this Warning screen with two options to continue to recovery (VolUp) or reboot
and selecting either of those options leads to these following screens: recover mode boot screen
But nothing happens then, It switches off again after 5-10 seconds on both the screens and I tried
Code:
adb devices
during all those stages but phone is not detected on PC
I need to recover some critical data from this phone which is paramount. Can someone guide me as how should i proceed with data recovery or extraction?
Click to expand...
Click to collapse
Seems to me that your issue is caused one of these 3 reasons.
1) the battery is failing
2) the internal sdcard is failing.
3) the internal storage is completely full and has no more room to cache files when booting or running.
If it caused by the lack of space to cache files, try booting into stock recovery then use the "wipe cache partition" option(do not choose the "factory reset" option) this will clear the cache and allow the device to boot if that was the issue.
If you know the exact firmware build number version that is currently installed on your device, you can download a copy of that specific build number firmware and flash it via Odin. As long as you use the exact version that you have, it should not wipe your data when you flash it. Then, if it works, you should be able to boot the device normally and retrieve your data.
If the issue is caused by a faulty battery or a faulty internal sdcard, it may fail during flashing, if this happens, it may render the device inoperable.
Sent from my SM-S767VL using Tapatalk
So I have a small problem that has giving me a headache the past few days. I got an old Nokia 6.1 from my mom & was asked to get the pictures & documents from it. I removed her pattern lock, because I was annoyed to use it all the time. A couple of days later, the phone has out of the blue a security pin. Which obviously no one knows, because no one configured it...
I spent hours looking different ways to extract the data or to bypass the lock & sofar I think I ran out of all the options.
Here is my current state & I would really appreciate some advice how to proceed.
1. Find my device:
The phone is on the list. But it shows that the last activity was on the 10th january & can't be reached it even though it's connected to the internet via my mobile data. Furthermore it seems that I wouldn't be able to unlock it anyways because it only gives me two options "Call the Phone" & "Set up secure & delete".
2. Installing Aroma to extract the data/remove lock files:
I can't do that because there is no custom recovery installed on the phone. Just the stock.
3. Installing a custom recovery:
I can't install/flash anything on the phone because the developer options, usb debugging & bootloader are not unlocked/enabled.
I came as far as being able to see my dive with adb on my pc, but I couldn't flash anything of it, because the signature fails.
I'm now posting this threar, to see if anybody has some advice for me, how I could get the pictures from the phone.
Thank you all in advance~
Push
The door to any Android device is ADB.
You say
came as far as being able to see my dive with adb on my pc,
Click to expand...
Click to collapse
hence ADB obviously is fullly working, means it should be possible to pull out the data in question by means of ADB.
Hi, thank you for your answer, I have expressed myself wrong/mixed adb & fastboot up. What I wanted to say, is that I can see the device via fastboot. Unfortunately not over adb.
{
"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"
}
as you can also see in the screen
If I understood what I read, there is no way to access the phone like this, is that correct?
Is there anything else I can do?
The Phone itself gives me an option to "Apply Update from ADB". My knowledge about this stuff is barely anything. But is there a way for example I could install/update an android version/new system without losing the internal data? At that point I don't care about the phone working properly, as I would like to get the pictures from it & root + wipe everything from it.
push
As "Apply Update from ADB" implies this option is used to flash an OS's update provided by OEM/carrier: updating an OS doesn't affect user data stored on phone.
Have you ever tried to exit phone's fastboot mode by running Fastboot commands
Code:
fastboot devices
fastboot reboot
I ended up factory resetting the phone. This Thread can be closed
If you have usb debugging on. Then you can use ADB. You can try to mount user partition and you can copy that partition.
Was trying to flash my CN ROM to the WW ROM.
Forgot to turn on USB Debugging in Developer Tools.
Couldn't get it work using HunterTik's guide.
Ran flashall_ATF from windows explorer.
Command prompt flashed on screen then vanished.
Tried running flashall_ATF in an elevated command prompt.
It failed but has apparently wiped the ROM. Device is now stuck in boot loop to fastboot.
Whatever option I choose reboots the device back to fastboot.
Windows can see the device but adb devices returns List of Devices Attached is blank.
How do I recover the phone from here?
Found this thread Rog phone 5 stucked on fastboot
Ran this command: fastboot -v flash all WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
Received these lines of text & now device boots to splash screen, gets stuck there, reboots a few times then sends me back to fastboot.
Still can't access recovery mode
{
"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"
}
Device is now back in a fastboot loop with no access to any options but power off & restart.
Your phone is broken
Buy a new phone and don't try to mess with it next time
Flash back to CN and try again.
or, get a dump of the official firmware, then sent boot / recovery / super over fastboot manually.
[Windows] Asus OTA payload auto extractor
Since nobody is doing it, I thought I'd package it and just put it here to help people This is a packaged version of Vm03's payload dumper make to work with windows without installing python and other stuff I also included a single line script...
forum.xda-developers.com
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
yurishouse said:
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
Click to expand...
Click to collapse
9008 rescue is the direction I was headed & you're right. Although, on reflection, the partitions were already deleted prior to running the 'fastboot -v flash all xx.raw' command. Not sure how, since that command was the only thing I did which resulted in something happening.
{
"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"
}
The only thing to do is to get a kernel exploit or something to turn **get_unlock_ability** into 1 qnd then just unlock the bootloader in fastboot mode.
Sound easy but will not be as it requires editing a root filesystem file.
ZModder said:
View attachment 5599971
The only thing to do is to get a kernel exploit or something to turn **get_unlock_ability** into 1 qnd then just unlock the bootloader in fastboot mode.
Sound easy but will not be as it requires editing a root filesystem file.
Click to expand...
Click to collapse
what? you didn't do anything. you found a story file talking about fastboot which anyone can radio access by sideloading a android root browser apk.... this has been known since the oculus go first dropped in like 2015....
you need a bootloader unlock code or script which only facebook can give you...it doesnt exist anywhere on the device and is not hidden...
you can try tool "mod" a system file but even if you somehow got the device to bypass the files intregity checks, it wouldnt actually work because you are "sandboxed". any changes you make will not alter system. functions or settings at all until you escape the "sandbox" which can only be done via a unlocked bootloader.
if still you somewhere tricked your device into saving any mods you made to system files, your device either will stop booting the OS or most basic device functions will stop worki g..
so i tried to go to fastboot mode. but something went wrong (i pressed vol- and vol+ and pwr at bad timing) now the screen is black, no buttons are working, you cant even hold pwr to reset the devices. and it looks like its a bootloader mode. i got this in my devicer manager.
but fastboot does nothing and adb even too.... what is this? is it any usefull?
raeumler said:
so i tried to go to fastboot mode. but something went wrong (i pressed vol- and vol+ and pwr at bad timing) now the screen is black, no buttons are working, you cant even hold pwr to reset the devices. and it looks like its a bootloader mode. i got this in my devicer manager. View attachment 5628753
but fastboot does nothing and adb even too.... what is this? is it any usefull?
Click to expand...
Click to collapse
That mode is used to flash the device but I doubt you can flash unofficial firmware.
Zillion said:
View attachment 5599971
The only thing to do is to get a kernel exploit or something to turn **get_unlock_ability** into 1 qnd then just unlock the bootloader in fastboot mode.
Sound easy but will not be as it requires editing a root filesystem file.
Click to expand...
Click to collapse
How about the new DirtyCred exploit?