Database Info

Restore Wifi Xoom with 3.1

While trying to unlock xoom, after the 3.1 update, I'm now stuck at the Dual Core screen.
Can anyone guide me to resolution?
Thanks in Advance.

what steps did you take?

I just followed the steps of:
This will ERASE your Xoom.
1) Get the Motorola USB drivers MOTODEV > Documentation & Tools > USB Drivers (you need to sign up on their but maybe you can google this and find it as well)
2) Get the Android SDK Android SDK | Android Developers (you only really need the fastboot executable file for your host OS)
2.5) - I will soon put together a windows pack for usb drivers & fastboot so you don't have to download all this stuff just to do one task.
3) Power off your Xoom
4) Press and hold the volume down button while pressing the power button
Even after the Xoom turns back on keep it pressed down and you'll see some starting fastboot protocol text on the top left of the screen.
5) Open a command window in your sdk\tools folder (not platform tools and depending on when you get the SDK you may need to copy over some DLL files)
6) type:
fastboot oem unlock
7) read the warning on your Xoom's screen, hit volume up if you wish.
You're now free to put whatever data you want on your tablet. Cheers.

robbiev80 said:
what steps did you take?
Click to expand...
Click to collapse
Did I miss anything?

Can anyone help me get back on track?

I was able to get my xoom restore with the following steps:
: This will wipe your Xoom
You're going to need to have the Android SDK installed. You can download it here.
Download the official HRI39 build from Motorola here.
Unzip the files in MZ600_HRI39.zip and move or copy them to the /platform-tools folder in your SDK folder.
Connect your Xoom to your computer.
Type adb reboot bootloader. Wait for it to reboot into the bootloader.
Type the following commands, waiting for each to finish before continuing:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
You've now successfully flashed your Xoom back to stock. Now it's time to relock the device.
Type fastboot oem lock, wait for the menu, the press the volume-down button. Then press the volume up button. It'll take a minute or so, then reboot. You're now completely back to stock and ready for the update.

[Q] Can't install apps, can't boot into recovery & can't do factory reset

Hey guys,
i keep it short.
Rooted Google Nexus S, CyberGR-MOD ICS. matr1x kernel.
1. Problem: Can't install/update apps. Error: Package file is invalid
Install from Play Store works, but update doesn't. Install from .apk file does not work.
Tried solutions:
- Wipe Play Store Cache, Dalvik Cache etc.
- Different transfer methods (USB, WLAN, 3G)
-> No solution
2. Problem: Can't boot into recovery
I get into fastboot and choose recovery, I get the google logo for a while and then just a black screen. ClockworkMod Touch Recovery was used.
Tried solutions:
- Installed older (non touch) CWM Recovery
- Installed AmonRa
-> Still not booting into recovery
3. Can't do factory reset
When choosing to reset the phone it restarts and just shows the google logo, I waited for an hour, then I removed the battery and restartet. SD-Card was wiped, but not the phone itself.
What I want is simple: Get a running OS, where I can install/update apps again. Any ideas?

Hey guys. I fixed it. In case anyone has similar problems, here's my solution. I use Windows, if you have a Mac or Linux OS, your commands may differ.
Warning: EVERYTHING on your phone will be erased and you will have the oiginal android ROM on your phone.
1. Your phone needs to be rooted and you ne need to have fastboot on your computer.
2. Go to: developers.google.com/android/nexus/images and download the right Image for your phone and place all files in a folder. For easier use, put them in the same folder as fastboot.
3. Boot your smartphone into fastboot and connect it to your computer.
4. Start a terminal window and navigate to your fastboot directory.
5. Type in these commands one after another and press ENTER after each command (The bold parts may differ, if you downloaded a different Image than I):
fastboot erase cache
fastboot erase userdata
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-imm76d.zip
6. Reboot your phone, in should now start with a fresh android os.

Installing Android on Nokia 2520 Tablet

I have been searching for a method to bypass the restrictive boot settings and install Android on my old Nokia Lumia 2520 Windows RT tablet. I have yet to come across a trustworthy method, although I have seen here that you can jailbreak the tablet. I know that is not the same as rooting it for running android, though. Does anyone have a strategy for this?

I also get a very easy and time consuming process of installing android on lumia devices from Nokia Lumia 2520 Manual- guideusermanual.com/product-name-lumia-2520-manual&po=672217&lang=English that is given below:
Full backup Win32diskimage to 7.8GB of memory if you want to return 520 Windows Phone:
sourceforge.net/projects/win32diskimager/
Windows device thor2 recovery tool for the bootloader to load:
support.microsoft.com/vi-vn/help/12379/windows-10-mobile-device-recovery-tool-faq
Link booloader, file gpt, twrp, rom cm13 :
drive.google.com/drive/folders/0B_4r4JB1Is2QRHZSbU5hVks3WWs
Update link CM14.1 (HOT):
drive.google.com/file/d/0B-TpiHEnTdWrUDFBZFVoQUNITTg/view?usp=sharing
Unlock bootloader: unlock bootloader via WP internals (search on google.com)
Backup WinPhone if you want to return to Windows Phone: Mass Storage mode via WP Internal mode. Use Win32DiskImage then full 8gb memory backup. (Store carefully, do not delete)
Proceed to install Android on Lumia 52X
On Windows: 4.1: In mode flash bootloader Nokia Boot Manager to the directory of the device recovery tool windows Shift + Right: Open command here Type the command: -mode rnd thor2 -reboot
When the phone to vibrate 1 knocker: mode rnd thor2 -bootlumiabootmgr
If it does all of the machine partition is oke, ph Nokia loud big logo will hang Rest assured, continue to flash the bootloader of the android: UEFI -partitionimagefile thor2 -partitionname uefiflash -mode “aboot-xxx.mbn file path
On the phone screen will display green NOKIA (already successful flash)
Remove the battery, insert the battery, the phone will not turn on the machine display Nokia logo. No problem, the machine has to be the android fastboot mode.
Boot ubuntu and switch terminals. repartition memory through Mass Storage Mode Mode, Type: fastboot devices (displays the first line device is xxxxx)
fastboot reboot-dload oem
GDisk sudo -l / dev / sdX to check the partition windows phone
sudo sgdisk –load-backup = “path file.gpt” / dev / sdX (to repartition)
deleted Win old data to install Android:
Remove the battery inserted, the holding power + silencer. USB cable connected to your computer and type: fastboot devices
fastboot format system
fastboot format userdata
cache fastboot format
fastboot flash recovery “twrp.img file path”
Then, remove the battery, keep the power + volume, wait times are boots twrp 1
Copy rom into memory, this time I was like 1 child Lumia phones running android true.
Wipe system, data, cache, cache dalvik
Flash rom
Reboot
To Fix Audio issues: Return fastboot mode by turning it off, hold the power button and the muffler to access the fastboot mode, turn on the terminal and type: fastboot devices
fastboot flash TZ “TZ file path”
fastboot flash modem “modem.img file path”

Did you ever get anywhere with this? I am in the same position. I have a brand new Nokia Lumia 2520 complete with keyboard cover which I bought in 2013. It was only out of the box for a couple of days as it was immediately clear that the operating system was useless. It has been gathering dust in a cupboard ever since. If I could get Android on to it I would be very pleased as it is a very nice piece of kit. Nokia shot themselves in the foot by opting for Windows RT instead of Android.

I would of thought that by now in 2020, someone, somewhere, would have possibly moved this project along already. A ported Android OS if not a community developed Win 10 RT for this 32-bit ARMv7 device. Since it's a dead OS, can we DL source code from MS?

Finepower C2 (Spreadtrum SC7731C) fastboot flash boot partition after repacking

Hello All,
The main question is How to repack boot.img rightly? (I mean do we need to sign it or specify the some device related properties).
Please see my requisites:
1) Product Market Name: finepower C2
2) Chipset: Spreadtrum SC7731C
3) Android OS Version: 6.0
4) Boot/Recovery partition was updated successfully via fastboot utility if original image was used.
I'm using the following command that flash images on device: fastboot flash boot boot.img OR fastboot flash recovery recovery.img && fastboot reboot
but I got the constant vibration after "fastboot reboot" command (see details below how it was repacked).
I'm trying to use the all famous tools to pack it back: imgtool (Mac OS), abootimg (Ubuntu), mkbootimg (legacy android tool).
Ramdisk was packed via mkbootfs tool or within using abootimg.
Could you please guide me how to solve this issue?

Infinix zero 5g 2023 TURBO X6815C (bootloader unlock/root/system-r/w) Ant-Man and the Wasp: Quantumania Edition

root infinix XOS 12 (Android 12)
Infinix Zero 5G Ant-Man and the Wasp: Quantumania Edition
Easy unlock
1. Enable developer options and turn on/allow OEM unlocking and enable USB debugging
2. Reboot to fastoot
Code:
Code:
adb reboot bootloader
3. Unlock bootloader via fastboot (you will be prompted to accept yes with volume up on phone.
Code:
fastboot flashing unlock
4. Setup and install MTK client Linux (fallow guide)
[GUIDE] [MTK] How to use MTKClient and set it up!
So most of you probably don't know what mtkclient is. It is basically an exploit which is used to boot any (mtk) phone into BROM mode (basically EDL for mtk) I am writing this guide especially for the RM6785 community. This tool is very useful...
forum.xda-developers.com
4. backup all partitions with MTKClient/MTKTool GUI (launch the mtk_GUI with su/root)
in mtk_GUI
Go to,
Read Partition(s) Tab and tick all boxes to be read/backup the partitions except data partition (internal storage)
Now you should have a backup of your files/.bin
5. copy boot_a.bin to your phone internal for magisk patching manually on phone
(Time of writing latest)
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
6. Rename (magisk renames the default .bin)
patched_boot_a.img to patched_boot_a.bin
7. Copy patched boot_a back to your computer/home folder.
8. flashing.
From fresh started Android reboot to fastboot.
Code:
adb reboot bootloader
DO THE NEXT 2 STEPS AT THE SAME TIME IN FASTBOOT.
(Fastboot commands)
Code: terminal
Code:
fastboot flash boot_a /path/to/patched_boot_a.bin
Code2: (disable verity/secure boot) use vbmeta_a.bin that you backed up from you're phone.
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a /path/to/vbmeta_a.bin
AFTER flashing above you should now have root
############## system r/w#############
If you want system R/W writable (full root) fallow next steps.
1. go to system r/w website and get this version tested here.
Official SYSTEM-RW v1.41 by lebigmac for Samsung Galaxy S23 Ultra and other devices
lebigmac's software
lebigmac
www.systemrw.com
Link to file above
11.21 MB file on MEGA
mega.nz
This must be run on the phone!
Step 1
Decompress (7zip) SYSTEM-RW_v1.41.zip to this directory on device. sysrw_1.41
Code:
/data/local/tmp
Step 2 in Android terminal type
Code:
Code:
su
cd /data/local/tmp/sysrw_1.41
chmod +x sysrw
./sysrw
This will build the new patched r/w super.bin in /data/local/tmp/sysrw_1.41/IMG
Use file explorer (fx-file explorer) to copy patched_super.bin to phones internal/storage and then copy to computer to flash with fastboot.
Step 3
Code:
On computer/PC with adb and fastboot flash super. (Should be around 8gb file)
Code:
Code:
sudo adb reboot bootloader
sudo fastboot flash super /path/to/patched_super.bin
sudo fastboot reboot
########################
Enjoy system r/w[/code]

Lposed

CPU Demensity 1080, can play most emulators (dolphin/athersx2) at 30-60 FPS,a really powerful gaming phone

Phone
Infinix Zero 5G Ant-Man and the Wasp Quantumania Edition

Any help please

Can elaborate this please. Im stuck at this step

Mtk-client has a user interface see photo
Step4 in mtk_GUI
Go to,
Read Partition(s) Tab and tick all boxes to be read/backup the partitions except data partition (internal storage)
Now you should have a backup of your files/.bin

Still can not change SELinux to permissive or install.... some madgisk modules..?? Assuming because the boot is reed only, wish system r/w worked on boot to as it contains the kennel..

Hi what version is your device? Is it v810? I was wondering if your device can boot into BROM mode.

Build number:
X6815C-H777A-S-GL-221010V451
Should work on
X6815
X6815B
And to get into BROM mode (to my understanding) on any mediatek CPU/phone simply power the device off with no USB connected...
Launch mtk_GUI with root, and it will ask to hold volume up or down while connecting the USB from a powered off state (try different button combinations)
Mtk _GUI is touchy!... with how it connects it usually takes me 2-3 attempts of rebooting and powering off my phone to get it connect/recognize in brom mode
(Might be worth noting)
If your Linux sysctl.conf has these security JIT settings
net.core.bpf_jit_harden=2
kernel.unprivileged_bpf_disabled=1
kernel.kexec_load_disabled=1
Or more...
mtk client will not recognize your devices... Simply move sysctrl.conf temporarily and reboot your Linux machine and try again

notreal456789 said:
Build number:
X6815C-H777A-S-GL-221010V451
Should work on
X6815
X6815B
And to get into BROM mode (to my understanding) on any mediatek CPU/phone simply power the device off with no USB connected...
Launch mtk_GUI with root, and it will ask to hold volume up or down while connecting the USB from a powered off state (try different button combinations)
Mtk _GUI is touchy!... with how it connects it usually takes me 2-3 attempts of rebooting and powering off my phone to get it connect/recognize in brom mode
(Might be worth noting)
If your Linux sysctl.conf has these security JIT settings
net.core.bpf_jit_harden=2
kernel.unprivileged_bpf_disabled=1
kernel.kexec_load_disabled=1
Or more...
mtk client will not recognize your devices... Simply move sysctrl.conf temporarily and reboot your Linux machine and try again
Click to expand...
Click to collapse
Damn sadly im on v810 now and it doesn't enter into BROM mode anymore or maybe am i doing something wrong but idk. I hope infinix will enable it again

Hnojohn said:
Damn sadly im on v810 now and it doesn't enter into BROM mode anymore or maybe am i doing something wrong but idk. I hope infinix will enable it again
Click to expand...
Click to collapse
This is why I don't update things, also it could be the setup Maby I'll post a Linux.iso with mtk client setup correctly

I still use Android apps from 2008 that still work on Android 12 fine