Database Info

[Q] How to install Lucifier 3006 rom on nokia lumia 710

Good evening sir I m tanmay gandotra currently using Nokia lumia 710
hardware rev 2.1 firmware 12070. First I have a locked bootloader I.e
Nokia dload so I flashed my phone using ncs and by Russian firmware
that u have provided. Now I have a unlocked bootloader I.e Qualcomm
cdma technology and I didn't format the disk. Now I m using the custom
rom fully-unlocked-os-new.nb by lucifier 3006 I m using Linux and the
command was dd if./os-new.nb of=/dev/sdX9. Now I have replaced
os-new.nb to full-unlocked-os-new.nb and my drive shown is sda6 while
running this command I get the error permission denied. Sir please tel
me the full guide to install custom rom on Nokia lumia 710. Which
directory I have to use while running this command in Linux please
reply me soon. I'd [email protected]

Did you run dd as root? You're trying to write directly to the block device, which usually requires elevated permissions (you could check and see what permissions are on /dev/sda6 or whichever block device it is, if you want to).

make sure that no removable devices are connected to pc other than ur device
after u connected ur device in qualcomm mode, open terminal(ctrl+alt+t) and enter "sudo fdisk -l"...it shows all the devices connected to ur pc....check for the device with 9 partitions such as sdb1,sdb2,sdb3,....sdb9....nly our device has 9 partitions...then enter the code "dd if./os-new.nb of=/dev/sdX9"...X=b or c or other(the device with 9 partitions)...and one more thing, name the file to "os-new.nb" or u have to change file name in the code...if u still have doubts...PM me..

Lumia Bricked
thanx for the reply sir, i followed the path as you told me. the command executed but only 512 kb coppied instead of 399 mb. now my phone is bricked .please help me to get my lumia 710 back in stead of bricked lumia which not at all responding. i tried ncs and nss but nothng worked... :'(

in ur post u said that ur drive is shown as sda6 which is not your device....ur device must show 9 partitions not 6...make sure u connect the phone in qualcom mode (power+vol [+])..
if u are quite sure that u have a qualcomm bl before dumping then u cant flash ur device using NCS...nly NSS can flash!!

[how to] lock/unlock your bootloader without htcdev(s-off required)

READ THIIS!
*this thread is for E8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-ian.anindya and a couple others have provided dumps. let me know and ill add you to the credits. if someone wants to provide screen shots,i can add those as well.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
(yes this is m7. i dont have an E8. if someone wants to provide correct screenshots,ill add them)
other useful threads:
remove tampered banner: http://forum.xda-developers.com/one-e8/general/how-to-remove-tampered-banner-t3019164
change mid without an eng bootloader: http://forum.xda-developers.com/one-e8/general/how-to-change-mid-eng-bootloader-t3019148

sorry for the delay,guys. hope you find it useful

This way doesn't wipe out all the data, right?

buggerman said:
This way doesn't wipe out all the data, right?
Click to expand...
Click to collapse
Correct. It will not wipe any data
Sent from my HTC One max

Good job.
Any way to do S-OFF to S-ON ??
greg

gregferns said:
Good job.
Any way to do S-OFF to S-ON ??
greg
Click to expand...
Click to collapse
Sunshine again..

windows 8 and above
am using windows 10 but it seems the required tool does not support the operating system
any other option for me?

cant get # prompt
hi, when i enter the Su command it says su not found and the prompt still remains $ instead of #. Is it something am not getting right or something. Thanks

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?

Teclast X98 plus ii (C2D6): Tablet not recognized in DNX fastboot

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!

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