Question Graphene OS - switch back to Google OS - Google Pixel 7 Pro

I tried Graphene OS for the past week and decided to go back to original.
- bootloader is unlocked
- am using Android Flash TOOL from here https://flash.android.com/
- Removed non-stock key prior to proceeding with Flashing
- i got to FastBoot screen during the Flash and the browser provided the following warning : '' Your device is being used by another program'' and then the Flasing process stopped.
- Am now back at the main Google screen.
- I believe Graphene OS already removed from device.
- Trying to initialize Android Flash TOOL once again, i accept ADB / Grant access to ADB keys - device does not show up in the tool anymore to flash stock OS. (see attached screenshot)
When I'm stuck at the main Google screen, I decided to factory reset.
Turned device off > Pressed Volume down > highlight “Recovery mode.” > “Wipe data/factory reset” > After reset completed, pressed the Power button to select “Reboot system now.”
{
"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"
}

Add new device ???? nothing ?.
What I always did with Google phones (family and friends who brought them to me to flash):
With the original ROM and before any manipulation
-go to developer mode + USB debugging + unlock bootloader.
-in fastboot, fastboot flashing unlock, reboot then reconfig of the phone.
-switch back to developer mode + USB debugging + USB connection to PC.
-adb reboot bootloader then adb kill-server (on the PC).
-connect to Android Flash Tool then do as if I was going to flash the original Rom (to make the phone recognized by Google) and stop the process before flashing.
I don't know if it's really useful to do all this but recently with 2 phones (Google 4A5G and Google 5 under GrapheneOS) putted back the ROM from Google before re-flashing on the 2 CalyxOS (support planned until January 2025) without any problem.
Last possibility for you, download the ROM factory, unzip it and launch the flash-all.bat in fastboot.

Tintin62 said:
Add new device ???? nothing ?.
What I always did with Google phones (family and friends who brought them to me to flash):
With the original ROM and before any manipulation
-go to developer mode + USB debugging + unlock bootloader.....
Click to expand...
Click to collapse
@yycDAAN This is the best solution: doing this stuff manually and not using a tool/site to automate things =).
But anyway, ensure that you have USB Debugging enabled. If you don't, then no image flashing will work manually or through sites that tackle it all for you - as they won't be able to detect the device (which appears to be your current problem).

Thank you guys for taking the time to help - much appreciate it
got into Fastboot mode. Android Flash TOOL recognized device and was able to install the original OS . When i restart phone, get the warning page :
''Your device is corrupt. It can't be trusted and may not work properly'' . I click CONTINUE and everything loads normally.
Is there anything I can do to ensure that ''Your device is corrupt.'' page stop showing up on Boot ?
EDIT : appears once bootloader is Locked, screen disappears
Leaving Thread up for reference.

Related

[Q] Xoom Root Problems

A few days ago I decided that I wanted to root my Xoom, so I went by a guide on how to do it. ( http://forum.xda-developers.com/showthread.php?t=1249798 )
I got into the bootloader, flashed on a new recovery, etc. Got the new kernal installed, so I reset my Xoom thinking I was done. Right now, it's stuck on the Motorola screen. Bring up the boot menu and try the recovery, it doesn't work. Tried the fastboot option, computer doesn't detect it. However, on the RSD mode, I did have some action with the computer. I'm not sure if it's a drivers issue, if the Xoom hates me... or what. :/
Anyone got any input on this?
I've done the following:
Used a different USB Cable
Used USBDeview to remove the drivers manually
Reset the Xoom using Vol up+Button on back
Ragequit, multiple times
Gone into Recovery, which led me to a Reading ODM Fuse: 1 screen where it stays
Tried the fastboot multiple times to no avail
Posted on xoomforums about this, no final answer.
Also,
{
"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"
}
Sounds like your relocked your bootloader, or you don't have a system image installed.
Start over from scratch - I used it to Root my Wifi Only Xoom and
my 4G LTE Xoom with no problems. Only took about 10mins - use this method:
Universal Xoom Root​
Thats right, this method will work for any xoom on any update - Including future updates!!!
Note: Unlike the similar method floating around on here, this also gives you an unsecured boot image.
-- Please Note: this thread is still a work in process and has been sped up by the arrival of the 4g Xooms --
Current requirements: adb & fastboot have been setup and you have an external sdcard for your xoom.
1. Setting up adb & fastboot
Coming Soon! (If you want to write this section for me and pm me it, thats fine !)
2. Downloading the rooting-update zip file.
Download the zip file from here.
Now place this on your external sdcard. - Sorry this is a requirement at the moment, like I said this is a bit rushed.
3. Flashing recovery
1. Download this Recovery image. (put this image in the same folder that holds the adb.exe most likely tools or platform tools folder.)
2. If your device is locked, now is a good time to unlock it.
To UNLOCK -
Code:
adb reboot bootloaderfastboot oem unlockfastboot reboot
3. Flash recovery
Code:
adb reboot bootloaderfastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
4. Flashing the Xoom-Universal-Root.zip file.
If you're in clockwork mod recovery you can continue (This recovery image will say it is clockwork mod) . If you're not looking at clockwork mod, then you need to repeat step 3 again.
In cwm, go into "install zip from sdcard" -> "Choose zip from sdcard", then select the Xoom-Universal-Root.zip file you downloaded.
Note: use the volume buttons to navigate and the power button to select
Reboot your device and then welcome to your rooted device!
Now reboot into recover and flash a new ROM of your choice - I like this one:
[ROM][ICS] Team Eos ICS 1.0.0
Flash ROM then, do not reboot yet. Flash GApps right after ROM Flash then reboot!
Welcome to your rooted device!
Downloads
Universal Xoom root - version 1.0

[GUIDE] Enable Fastboot and install TWRP on Yes Altitude M631Y/China Mobile A1s

The Fastboot mode of M631Y is locked by the phone manufacturer. Flashing a leaked old version of phone firmware will enable your phone to enter Fastboot mode. After entered Fastboot mode, boot to TWRP and you will able to install it for replacing the phone stock recovery.
Warning: You will void your phone warranty when you start the process. Your phone maybe bricked during the process. I do not take any responsibility for any damage.
Before you start, backup all your data. Your data will be erased during the process.
Step
1. Enter Download Mode
Shutdown your phone first.
Method 1
Press Vol. Up + Vol. Down and plug the USB cable to enter Download Mode.
Method 2
Press Vol. Up + Power button at the same time. After the display is on, release the Power button. Click this button circled to enter Download Mode.
Method 3 (For bricked phone)
If you are unable to enter the Download Mode of your phone with the above method. You can try to short points on the main board to enter Download Mode.
Remove the back cover and the battery.
Remove the screws
Remove the cover
Install the battery
{
"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"
}
Short the points point here and plug the USB cable.
I use a touch screen stylus pen to short those points.
Your phone should be turned on and in Download Mode.
I don’t what is the function of those points. I think the EDL pin/ test points maybe are located at there. Therefore, the phone will enter EDL mode when the phone is booted with the shorted pins.​2. Flashing the old version firmware(M631Y_02.10.00RDD_HK.00) with QFIL
3. Enter Fastboot Mode and boot to TWRP
Code:
fastboot boot TWRP-3.2.3-TwrpBuilder-m631y-2018-09-06_09-50.img
4. Install TWRP
If you don’t mind using a development version of ROM, then finish. If you mind, continue to install a newer version of ROM.
The version to install here is CMA1S 02.23 HK. The latest version for CMA1s HK edition should be 02.25. I tried install 02.25 and 02.24, but it seems that both cannot work with the older version of Boot and ABoot.
Install update.zip using TWRP
Install downgradeto210All.zip. This will downgrade the firmware and Boot back to version 02.10
Install upgradeto223modem.zip to upgrade the Modem back to 02.23.
Install TWRP again
Below are the suggestions for deleting the useless/infected system app preloaded. Please mount the system partition with write permission in TWRP. Delete the folder mentioned.
Infected stock camera
/system/vendor/app/QuanNengCamera
CMHK apps
/system/vendor/operator/app
CmccAnalyser
/system/priv-app/CmccAnalyzer
Cmccsaletracker
/system/app/Cmccsaletracker
Files
TWRP
github.com/TwrpBuilder/android_device_yes_m631y/releases/tag/TWRP-3.2.3-TwrpBuilder-2018-09-06_09-50
Rom
mega.nz/#F!GypEhazR!2E3fuW4KdxYoE4S53oDUOg
Android SDK Platform Tools
developer.android.com/studio/releases/platform-tools
Credits
TWRP Builder team for building the TWRP for this phone
The person uploaded the old development version phone firmware on web

Trying to backup a locked Android Phone

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.

How To Guide How To: Region Switch on Nord2T

Hello again everyone. This is a quick guide on how to change Regional firmware on our Nord2T device (ie going from CPH2399 to CPH2401)
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!​
Before we get started I would recommend unlocking the bootloader (unsure if this is a necessity but my device was unlocked at the time of trying so I would recommend users do the same)
1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped)
2 - Download and Install Fastboot Enhance from HERE
3 - Download the IND rollback package from HERE
4 - Extract the rollback package zip to your PC (the only file you need once it is unzipped is payload.bin)
5 - Connect your device back to PC and reboot to fastboot yet again.
Code:
adb reboot fastboot
6 - Once in fastbootd open Fastboot Enhance on PC and you should see your device in the "Fastboot Visualization" tab.
Make sure to click on "Ignore unknown partitions" on the bottom of the screen. Then click on the "partitions" option and under partitions and delete every file that ends with "cow" refer to screenshot, just select and delete.
{
"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"
}
7. Click on "Flash payload.bin" and browse for the payload.bin you extracted earlier.
8. Once flashed you can reboot (recommended to either factory reset from settings after the device restarts or wipe data in fastboot for a smoother experience.
This is only tested on a Global device using firmware version CPH2399_11_A.17 and flashing IND CPH2401_11_A.17 ROLLBACK PACKAGE!!
Subsequent updates will now be on the IND branch for your device also.
Hope this helps someone out!
If anyone has any questions/input/recommendations please feel free to discuss below and any issues we will help to resolve them.
Have a good day peeps

[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

Categories

Resources