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?
Related
Hello
First, the Driver must be installed on the machine before then.
1-6 commands can be used with the open marriage Debug Mode only.
7-9 can be used with the machine that faithful into Fastboot Mode only.
Profile commands.
1.Check Device used to check the connection of the machine mode ADB.
2.Reset User Lock Code using the tools that are in the data is not lost.
3.Reset Gesture Lock machines that are used to draw a line through the data is not lost. After the installation is complete, it will fire up. Then draw anything for a closed lock.
4.Reset GMail using the machine to try to unlock the machine several times to enter to unlock.
5.Wipe Data used to resolve the symptoms or slow down. Or that an error or some missing.
6.Reboot to reboot your PC or from adb shell.
7.Check Device On Fastboot Mode to check the connection of the machine mode FastBoot.
8.Wipe Data / Cache On Fastboot Mode This command is available only Fastboot Mode to resolve the symptoms or slow down. Or that an error or some missing. That is often found in the CPU Spreadtrum.
9.Exit Fastboot Mode to reboot your PC or exit FastBoot.
Help.
Press the number that corresponds to the condition of the machine and then hit enter.
Worked perfectly on a Tablet Platinum PL-5002
Had a friedn with a Tablet Platinum PL-5002 and it was locked, asking for his gmail password...we tried everything to get it to work and was about to give up when we ran in to this and it worked on the first try.
Recently I found out there was a kit kat update for my droid ultra it downloaded the update using 4G LTE and now and decided to install it then the phone shuts down and powers back up on its on I thought it was part of the update but this is the 100th time it's done it ive been waiting 8 hours for it to stop but it just keeps going it's not even showing any sign that it is updating!!!
I tried booting into recovery to factory reset it but whenever I select recovery it just boots up the phone normally HELP PLEASE!!!
response
droidusr2014 said:
Recently I found out there was a kit kat update for my droid ultra it downloaded the update using 4G LTE and now and decided to install it then the phone shuts down and powers back up on its on I thought it was part of the update but this is the 100th time it's done it ive been waiting 8 hours for it to stop but it just keeps going it's not even showing any sign that it is updating!!!
I tried booting into recovery to factory reset it but whenever I select recovery it just boots up the phone normally HELP PLEASE!!!
Click to expand...
Click to collapse
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Thanks
Thank you so much currently I can't try out your method but it looks like it could work THANK YOU SO MUCH I'm going to try tonight and I'll tell you how it went. I really don't mind factory resetting as long as it saves my phone im all right thanks again :laugh:!!!
Pacnet_ said:
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Click to expand...
Click to collapse
Will factory reset erase root??
One more thing I actually am currently rooted by using RockMyMoto so I think that is why the update didn't work but 1 last question when I factory reset will it erase root? I don't mind if it erases root but my main concern is that if root somehow stays I won't be able to do the software update.
Pacnet_ said:
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Click to expand...
Click to collapse
Tried the method and it worked!!
I tried what you said and it worked perfectly but it still remembers my Wifi, wallpaper and all it showed the setup screen and I set it up so hopefully im in the clear the phone is downloading the update right now.
It will not allow the update and you will still end in boot loop. Need to remove root first: http://forum.xda-developers.com/showthread.php?t=2577029
so i have managed to come across a couple of Imerj Blugroov phones its a concept dual screen dual core android phone running 2.3.4
looking for any information on changing the Rom to something newer. i have heard they were using the nexus firmware for testing.
model number comes up as : New Era DV21 (US)
i have only been able to find a Chinese site that mentions this phone but no other information anywhere.
contact for link
if anyone knows anything about these please contact me
kkrakker said:
so i have managed to come across a couple of Imerj Blugroov phones its a concept dual screen dual core android phone running 2.3.4
looking for any information on changing the Rom to something newer. i have heard they were using the nexus firmware for testing.
model number comes up as : New Era DV21 (US)
i have only been able to find a Chinese site that mentions this phone but no other information anywhere.
contact for link
if anyone knows anything about these please contact me
Click to expand...
Click to collapse
The device is based on Blaze board.
You have a root adb shell already. Start from Blaze from TI builds.
Quite late this post but
-Use it from Linux. Windows is not supported.
-Check dmesg when you plug in the USB. Check for vendor and device
-ID's and add the rules in /etc/udev/rules.d/51-android.rules
-You would need android tools, SDK as they were in 2010 and also fastboot
version from 2010 or 2011 (Ubuntu).
-unplugg the USB from the PC
-Hold the mute button while power on
(power and volume up or down would go to recovery mode, indicated by some vibrations)
-Release power when the circle LED lights up (some vibrations might occur)
-Release the MUTE circle LED turns off, menu shows on and back LED is on
-Plug the USB cable to PC
-type in a terminal
$sudo fastboot devices
Presume you have a build for Blaze Board ( Gingerbread) as it was back in 2010
$sudo fastboot flash bootloader u-boot.bin
$sudo fastboot erase environment
Power off the device
Hold the mute button while power on
Plug the USB cable in
Check if PC sees the device
$sudo fastboot devices
$sudo fastboot flash boot boot.img
$sudo fastboot flash recovery recovery.img
$sudo fastboot flash system system.img
$sudo fastboot flash userdata userdata.img
$sudo fastboot flash cache cache.img
$sudo fastboot erase environment
$sudo fastboot reboot
The device partition table is:
ptable 0 128KB mbr.bin Master Boot Record (MBR) for the eMMC device
xloader 0x100 128KB MLO.emu X-Loader bootloader
bootloader 0x200 256KB u-boot.bin U-Boot bootloader
environment 0x400 128KB env.txt U-Boot bootloader environment
boot 0x500 14MB boot.img Kernel and ramdisk
recovery 0x7500 14MB recovery.img Kernel and recovery ramdisk
system 0xFB04 768MB system.img Android system image
userdata 0x1900E6 1GB userdata.img Android data partition
cache 0x391DA9 1GB cache.img Android cache partition
media 0x593A6C remaining none Android SDCard partition
Hi,
I am stuck with my tablet.
1. With a linux live usb I've removed all the partitions of the device. (create new partition table GPT)
2. Now when I boot, I see the BIOS only. I can also boot in DNX fastboot mode.
Nevertheless, fastboot cli and Phone flash tool doesn't recognize my device.
I've well installed the Intel driver called IntelAndroidDrvSetup1.10.0.exe and if I go to the Device Manager, I can see my device as Intel Android ADB Interface with a ! saying:
Code:
This device cannot start. (Code 10)
An invalid parameter was passed to a service or function.
How to make windows recognizing my tablet?
Please help me to solve this problem.
Thank you!
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