This is a CWM-Based Recovery 6.0.4.6 Touch Recovery for Xperia SP
Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!
[ info ]
This recovery is built from CWM Recovery 6.0.4.6 sources and is integrated into stock kernel... I call this an advanced stock kernel with recovery!
the core kernel (zImage) is exactly the same as the one supplied by Sony for that particular firmware... only the ramdisk is changed to add recovery and other features!
[ credits / special thanks ]
Koush - for the brilliant work & coding on CWM recovery
CyanogenMod and FreeXperia Team (especially jerpelea) for too many things
ME for creating this for u guys!
[ Requirements ]
Bootloader unlocked
working fastboot
STOCK ROM FW:
4.3 -> 12.1.A.1.201 - v02, v03
4.3 -> 12.1.A.0.266 - v01
or ROMS BASED ON THAT FIRMWARE
[ features ]
standard CWM recovery 6.0.4.6 - TOUCH RECOVERY!
adb debugging is enabled by default in OS
fixed root remount in ramdisk
TIP: if u are experiencing very slow backup in CWM do this
[ WARNING ]
for flashing this kernel you WILL NEED TO UNLOCK BOOTLOADER! Check this thread for more info...
UNLOCKING BOOTLOADER WITHOUT TA BACKUP WILL LEAD TO IRREVERSIBLE LOSS OF DRM KEYS!!!
[ how to flash this kernel ] (via fastboot)
download the kernel image
save the SP_DooMLoRD_AdvStkKernel_FW-XXX_vXX.elf to the folder containing fastboot binary
flash the SP_DooMLoRD_AdvStkKernel_FW-XXX_vXX.elf using fastboot:
Code:
fastboot flash boot SP_DooMLoRD_AdvStkKernel_FW-XXX_vXX.elf
reboot from fastboot
Code:
fastboot reboot
the device should now start booting
enjoy!
[ how to enter recovery ]
when you see the Sony logo and the LED light turns green/blue/red keep tapping/pressing VOLUME UP key
[ how to Root ]
for instructions on how to root please check this post
[ sources ]
https://github.com/DooMLoRD/android_device_sony_huashan
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
OR
you can buy one of my awesome apps from Play Store!
[ download links ]
PLEASE DO NOT MIRROR, REDISTRIBUTE, REPACK MY FILES
NEW:
Advance Stock Kernel with Recovery v03 (FW:12.1.A.1.201) {MIRROR}
MD5HASH: 56cc37aa72c2a3a727341299bb1cf441
OLD:
Advance Stock Kernel with Recovery v02 (FW:12.1.A.1.201) {MIRROR}
MD5HASH: 49d4b03efc9f64369d7001e42f373c2f
Advance Stock Kernel with Recovery v01 (FW:12.1.A.0.266) {MIRROR}
MD5HASH: 2ebdc746553c622699f65c0c6fe95117
{
"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"
}
enjoy!!!
Rooting Instructions
[ how to root ]
once you have flashed the kernel from the 1st post
download the latest SuperSU update.zip from: http://download.chainfire.eu/supersu
save it on sdcard of device
reboot into recovery
flash the supersu update.zip
reboot from recovery into OS
you should now get proper root access!
[ installing busybox ]
it is highly recommended to install busybox after rooting!
just go to andorid play store and download the busybox installer.
once the installer is downloaded, install busybox in /system/xbin
reboot device after install and thats it!
regards,
DooMLoRD
Great DooMLoRD, You Are so fast!
Very thanks for supporting XSP...
Amazing.
I assume, locked bootloader you´re working on?
still not want to unlock my bootloader
Amin.HVS said:
Great DooMLoRD, You Are so fast!
Very thanks for supporting XSP...
Click to expand...
Click to collapse
thanks! if i have device in hand its easier to support it
thank you all for donating device to me!
[email protected] said:
Amazing.
I assume, locked bootloader you´re working on?
still not want to unlock my bootloader
Click to expand...
Click to collapse
for now no... there is a way to root on locked bootloader... but I am busy right now and have pathetically slow internet bandwidth! anyways I am sure @[NUT] can post that upgrade with root package...
@[NUT]
the partition format for the Xperia SP is different!!! dont flash anything to "boot", booting kernel is at Kernel
FYI:
Code:
C:\Users\DooMLoRD>adb shell ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2014-02-13 01:53 Boot -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-02-13 01:53 Boot2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-02-13 01:53 Cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-02-13 01:53 FOTAKernel -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-02-13 01:53 Kernel -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-02-13 01:53 LTALabel -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-02-13 01:53 System -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-02-13 01:53 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-02-13 01:53 TZ -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-02-13 01:53 Userdata -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-02-13 01:53 apps_log -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-02-13 01:53 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-02-13 01:53 modemst1 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-02-13 01:53 modemst2 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-02-13 01:53 ramdump -> /dev/block/mmcblk0p9
Thanks for the pointer @DooMLoRD, it also pointed me to the mistakes I made for the T
Building XZDualRecovery for the SP as we speak.
Once this has been tested successfully I can do the update package :good:
http://forum.xda-developers.com/showthread.php?t=226160
Watch for it's release and help me debug it!
-- RELEASED NOW --
how do i unlock BL in 4.3? just the same way i did in 4.1? thanks, need root badly.
The RAM consumption bug is also present on this kernel...
I was running the stock kernel without recovery on leaked ROM for 3 weeks without issue.
wait, wait. the link you posted on how to unlock bootloader requires root. however, i am not rooted (obviously) so i cannot unlock bootloader. but rooting requires unlocked bootloader and mine's locked, so what should i do?
papawil01 said:
wait, wait. the link you posted on how to unlock bootloader requires root. however, i am not rooted (obviously) so i cannot unlock bootloader. but rooting requires unlocked bootloader and mine's locked, so what should i do?
Click to expand...
Click to collapse
Unlock BL doesn't require root...
Sent while my supervisor wasn't looking
@non4 said:
Unlock BL doesn't require root...
Sent while my supervisor wasn't looking
Click to expand...
Click to collapse
yeah but backing up DRM keys does right?
Any working method for locked bootloader?
is this correct?
1. flash stock .254
2. root stock 254
3. backup TA
4. unlock bootloader (.254)
5. flash .266 (with unlocked bl)
6. root .266 (using doomlord's method)
7. restore drm keys from .254 (wc will also relock bl)
thanks. badly need root for .266 -_-
papawil01 said:
is this correct?
1. flash stock .254
2. root stock 254
3. backup TA
4. unlock bootloader (.254)
5. flash .266 (with unlocked bl)
6. root .266 (using doomlord's method)
7. restore drm keys from .254 (wc will also relock bl)
thanks. badly need root for .266 -_-
Click to expand...
Click to collapse
That should do fine, but at step 7 you should also flash the stock kernel back, failing to do so will end up in a (recoverable) softbrick.
[NUT] said:
Thanks for the pointer @DooMLoRD, it also pointed me to the mistakes I made for the T
Building XZDualRecovery for the SP as we speak.
Once this has been tested successfully I can do the update package :good:
http://forum.xda-developers.com/showthread.php?t=226160
Watch for it's release and help me debug it!
-- RELEASED NOW --
Click to expand...
Click to collapse
I have Locked BL.
If need any testing, or other info, please let me know.
[NUT] said:
That should do fine, but at step 7 you should also flash the stock kernel back, failing to do so will end up in a (recoverable) softbrick.
Click to expand...
Click to collapse
Wow, the legendary nut replied to me anyway, stock .266 kernel right? is it available already?
papawil01 said:
Wow, the legendary nut replied to me anyway, stock .266 kernel right? is it available already?
Click to expand...
Click to collapse
Heh
Just use the 4.3 kernel from the FTF (wipe none, exclude everything but the kernel)
After install this, I've problem with ram managment, back button in some app and games, and re open launcher
Sent from my C5303 using XDA Premium 4 mobile app
[NUT] said:
Heh
Just use the 4.3 kernel from the FTF (wipe none, exclude everything but the kernel)
Click to expand...
Click to collapse
got it, thanks. btw, one last question. do you happen to know what .ftf file should i download? im in the Philippines and not quite sure about which one to download, since there isn't a global generic one yet.
papawil01 said:
got it, thanks. btw, one last question. do you happen to know what .ftf file should i download? im in the Philippines and not quite sure about which one to download, since there isn't a global generic one yet.
Click to expand...
Click to collapse
Unless you have a vendor build (the 6 on the end of your model number usually gives that away), there should not even be a very big difference. Baseband should be the same and the ROM is generic by nature. Only some customization differences which mean some more or less apps.
In your current ROM you can find your build.prop, use that to find out your own customization and use this guide to help yourself build your own FTF.
Good luck
Related
Introduction
This thread describes an experimental mod that allows you to boot into other boot images stored in your sdcard.
The N1 does not have enough internal memory to store more than one android image, thus we have to use the sdcard for this.
NOTE:
This mod is experimental, and for advanced users only
Requirements (READ THEM CAREFULLY):
- A rooted and unlocked phone
- A FAST enough sdcard. This mod will work with any sdcard but I'd suggest at least a Class 4 card for performance reasons
- Your sdcard should have enough free space. Each 'boot option' that you create reserves 400MB of space in your sdcard
- In order to create a new boot option, you need a flashable zip over CWM of the ROM you wish to boot to. The flashable zip of the ROM is the same that is used for usual ROM installation. Also the zip should be using the latest update-binary format as is scripted in updater-script (e.g. the mount command takes 4 args, etc.)
Advanced Information regarding the process
- The mod requires a boot.img that is flashed by the zip. This is used for extracting the ramdisk, commenting out the mount mtd commands and using this ramdisk for chrooting into the ROM environment
- If no boot.img is existing, the ramdisk is picked up from /sdcard/ramdisk/
- The kernel used for booting all boot options is the one installed in the phone's boot mtd. This means that you need the respective kernel modules (e.g. WiFi) for this kernel, not the one that is bundled in the ROM that is multibooted. For example, if your main ROM is CM, pick the kernel modules from this one and push them to the multibooted ROM's /system/lib/modules/
Multiboot mod Installation
Download: N1_CWM-4.0.0.5-nobodyAtall-r2.img
Install via fastboot
Code:
Copy N1_CWM-4.0.0.5-nobodyAtall-r1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash N1_CWM-4.0.0.5-nobodyAtall-r1.img
Install via adb
Code:
adb push N1_CWM-4.0.0.5-nobodyAtall-r1.img /sdcard/
adb shell 'flash_image recovery /sdcard/N1_CWM-4.0.0.5-nobodyAtall-r1.img'
adb reboot recovery
Multiboot ROM Installation
- Boot into the recovery and navigate to the new 'multiboot' menu. There you'll see the following options:
Boot into selected option!
Select default boot option
Unset default boot option
Create boot option from zip
Delete existing boot option
Flash zip to boot option
- Select multiboot->Create boot option from zip and then pick the flashable ROM zip. Be patient, this step reserves the space and flashes the selected zip to the system.img in the sdcard
- If you need to flash additional zips for this ROM, Select multiboot->Flash zip to boot option, pick your newly created boot option and then pick the zip you need to flash.
- Select multiboot->Select default boot option and pick your newly created boot option
- Select multiboot-> Boot into selected option! (first boot will take some time depending on your sdcard speed).
To verify you have booted to your newly created boot option, check 'adb shell mount', it should say that /system /data and /cache is mounted from /loop* devices and not from mtd*
{
"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"
}
ROMS verified to multiboot
Well, any ROM should be able to multiboot provided the requirements stated above are covered. The following ones have been verified to work:
[ROM] CyanogenMod-7.1 for Nexus One
[ROM] NEXUS N1 Passion MIUI.us Presents MIUI Pure English [AOSP]
CM 7 ExtremeMod ROM by Ken Mood
Uninstall
- Normal reboots will boot from the phone's mtd partitions.
- This mod makes no changes to your phone's mtd partitions. Flashing a new recovery will uninstall the old one obviously.
- To remove installed boot options, navigate to multiboot->Delete existing boot option and pick you choice. Alternatively remove the boot option you want from /sdcard/clockworkmod/multiboot/
Disclaimer:
I can't be held responsible if this mod bricks your device / trashes your sdcard or makes it explode in your hands! Use it at your own risk!
Changelog:
(1/7/11) N1_CWM-4.0.0.5-nobodyAtall-r2.img
Fixed bug that flashed the multiboot ROM kernel in the phones kernel partition
Improved error reporting
(30/6/11) N1_CWM-4.0.0.5-nobodyAtall-r1.img
First version of CWM recovery providing the multiboot options
woww thanks
Well, this could be freaking awesome. I'll check it out at work
Nice one. Can we use CM nightlies that came after the RC?
method77 said:
Nice one. Can we use CM nightlies that came after the RC?
Click to expand...
Click to collapse
You can use it with any CM7 ROM
I am interested in this, i'm surprised that it hasn't created more of a stir.
I have installed the recovery, but don't want to do anything else without Nandroiding first. Only Nandroid seems to get stuck on "Backing up system..."
Any i doing something wrong?
Hello shorza,
To be honest, I've only been testing the multiboot part.
However, I think that backup works fine here:
Also the backup folder is created correctly:
~ # ls -la /sdcard/clockworkmod/backup/2011-07-01.06.49.58
drwxrwxrwx 2 root root 4096 Jul 1 06:52 .
drwxrwxrwx 5 root root 4096 Jul 1 06:49 ..
-rwxrwxrwx 1 root root 93489792 Jul 1 06:52 .android_secure.img
-rwxrwxrwx 1 root root 3670016 Jul 1 06:50 boot.img
-rwxrwxrwx 1 root root 37359168 Jul 1 06:52 cache.img
-rwxrwxrwx 1 root root 184136832 Jul 1 06:51 data.img
-rwxrwxrwx 1 root root 222 Jul 1 06:53 nandroid.md5
-rwxrwxrwx 1 root root 4194304 Jul 1 06:50 recovery.img
-rwxrwxrwx 1 root root 146908608 Jul 1 06:50 system.img
On another note, I'll be doing an update today to fix some bugs related to multiboot.
CWM 4.x has problems backing sd-ext, so that might be the reason why you don't see it (your pic shows you don't have an sd-ext partition to backup) and shorza does. It is also the reason why I haven't tried this yet - if it was based on AmonRa's I'd have jumped immediately, but since it is based on CWM I wanted first to see some feedback here...
Thanks for the help. Backup eventually worked, it just took a long time.
The problem is after zipping a new rom in multiboot, selecting it, then trying to boot into it, it took too long and I lost patience. It looked like it froze.
I'll try again tomorrow.
Maybe my sdcard is too slow.
shorza said:
Maybe my sdcard is too slow.
Click to expand...
Click to collapse
You need to be patient. It takes a long time to boot (especially for the first boot) and if the recovery seems frozen, this is a good sign - it means it's booting.
Posted -r2.
This fixes a bug that would flash the multiboot ROM's kernel to the phone's kernel partition. Also improves logging in case of errors.
Testing this out right now ... just got latest cyanogenmod nightly and latest miui (as of today) going on it and just switched back and forth. sucks about having to go into recovery to switch, needs to have a boot option when starting the phone haha.
So wifi doesn't work in the latest version of miui.us when using it as a multiboot option. such says in logcat "Failed to load Wi-Fi driver." it works when the rom is installed as normally so it must be the kernel from this application. but wifi on cyanogenmod works so that is good.
Will this work like a nandroid backup where it saves everythn from my last boot? Or will it save everythn on that same img. when i switch roms
looking at the directory structure, per multiboot rom it saves the boot.img, cache.img, data.img, and system.img .... I don't know how it uses them, but linux is magical in mounting images as a partition, doesn't have to be physical
This is because the ROM is run using the device's kernel and not the one that comes with the ROM as stated in the first post.
To make wifi work, simply copy your wifi kernel module from /system/lib/modules to this same did within the multibooted ROM.
Ellises said:
So wifi doesn't work in the latest version of miui.us when using it as a multiboot option. such says in logcat "Failed to load Wi-Fi driver." it works when the rom is installed as normally so it must be the kernel from this application. but wifi on cyanogenmod works so that is good.
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
This actually works pretty well, however, the phone get quite hot.
[Q]Bug fixed??
I succeed multibooting
I got miui(main)&CM7(sub)
but subrom,cm7 can't use wifi
so I changed kernel but failed
and display
[mount expects 4 3args]
[error /sdcard/xxx... ]
[ status7 ]<<maybe
If you know what's the problem, plz teach me the way
thx and pardon my English
[ info ]
so friends i present to u Advanced stock kernel for Xperia U!
i dont have device with me but a friend of mine requested me to make this kernel so here it is
now u dont need to flash pre-rooted system images
the main kernel (zImage) is stock from FW 6.0.B.1.564
i MAY work on integrating recovery into this advanced stock kernel IF AND WHEN i get time...
thanks to my friend Jozinek for sending the kernel.sin & Amor Cbr, Pwng3 for testing it on their phone!
[ disclaimer ]
I AM NOT TO BE HELD RESPONSIBLE IF U DAMAGE UR PHONE / SPILL UR COFFEE / MISS UR ALARMS / ANY OTHER CALAMITY/MISHAP
[ features ]
[v01 onwards] added support for init.d scripts (/system/etc/init.d)
[v01 onwards] added support for userinit scripts:
if sd-ext is mounted then it will execute /sd-ext/userinit.sh & shell scripts in /sd-ext/userinit.d/ folder
also scripts in /data/local/ will be executed... it will execute /data/local/userinit.sh & shell scripts in /data/local/userinit.d/ folder
[v01 onwards] autorooting (prerooted)
su binary & superuser.apk will automatically be installed by kernel
busybox (1.18.4) gets installed at /system/xbin/
[v01 onwards] insecure ramdisk
ramdisk is insecure (ro.secure=0)
adb server is persistent
usb debugging enabled
rootfs and /system mounted as rw
[ requirements ]
stock Sony 6.0.B.1.564 FW
bootloader unlocked
working fastboot
you have read this thread
[ how to install this kernel ]
download the kernel.elf
save the it in the folder with fastboot binaries (fastboot.exe files)
power down device
start device in fastboot mode
use the following command to flash the kernel.elf
Code:
fastboot flash boot kernel.elf
reboot phone and enjoy the kernel
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
[ downloads ]
[Xperia U] Advanced Stock Kernel (FW: .564)
[ MD5HASH: 6507a237005d8ce7b5b7c4d7655ae4a2 ]
TEST OUT AND LET ME KNOW ASAP!
incase the device doesnt boot, open any stock FTF in FlashTool and flash the kernel.sin (with loader.sin selected) ONLY to get back to stock kernel!
{
"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"
}
cheers!
Nice to see 1st kernel for U?
Too bad i have a locked bootloader
DooMLoRD said:
[ info ]
so friends i present to u a TEST Advanced stock kernel for Xperia U!
i dont have device with me but i hope some of u with the device can test it out and let me know...
if it works then u dont need to flash pre-rooted system images
the main kernel (zImage) is stock from FW 6.0.B.1.564
i MAY work on integrating recovery into this advanced stock kernel IF AND WHEN i get time...
thanks to my friend Jozinek to provide me the kernel.sin
[ disclaimer ]
I AM NOT TO BE HELD RESPONSIBLE IF U DAMAGE UR PHONE / SPILL UR COFFEE / MISS UR ALARMS / ANY OTHER CALAMITY/MISHAP
[ features ]
[v01 onwards] added support for init.d scripts (/system/etc/init.d)
[v01 onwards] added support for userinit scripts:
if sd-ext is mounted then it will execute /sd-ext/userinit.sh & shell scripts in /sd-ext/userinit.d/ folder
also scripts in /data/local/ will be executed... it will execute /data/local/userinit.sh & shell scripts in /data/local/userinit.d/ folder
[v01 onwards] autorooting (prerooted)
su binary & superuser.apk will automatically be installed by kernel
busybox (1.18.4) gets installed at /system/xbin/
[v01 onwards] insecure ramdisk
ramdisk is insecure (ro.secure=0)
adb server is persistent
usb debugging enabled
rootfs and /system mounted as rw
[ requirements ]
CLEAN un-rooted stock Sony 6.0.B.1.564 FW along with FTF ready for flashing via FlashTool
bootloader unlocked
working fastboot
you have read this thread
[ how to install this kernel ]
download the kernel.elf
save the it in the folder with fastboot binaries (fastboot.exe files)
power down device
start device in fastboot mode
use the following command to flash the kernel.elf
Code:
fastboot flash boot kernel.elf
reboot phone and enjoy the kernel
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
[ downloads ]
[Xperia U] Advanced Stock Kernel (FW: .564)
[ MD5HASH: 6507a237005d8ce7b5b7c4d7655ae4a2 ]
TEST OUT AND LET ME KNOW ASAP!
incase the device doesnt boot, open any stock FTF in FlashTool and flash the kernel.sin (with loader.sin selected) ONLY to get back to stock kernel!
cheers!
Click to expand...
Click to collapse
1st kernel for my SXU..I try it update : it works
how to recovery on xperia U
Amor Cbr said:
1st kernel for my SXU..I try it update : it works
how to recovery on xperia U
Click to expand...
Click to collapse
great so can u confirm that the device boots with this kernel? also does the system get rooted?
P.S.: recovery is currently NOT integrated
DooMLoRD said:
great so can u confirm that the device boots with this kernel? also does the system get rooted?
P.S.: recovery is currently NOT integrated
Click to expand...
Click to collapse
Working perfectly. The system is rooted
How do I check if the device is booting with this kernel?
Thanks a ton btw!
Pwng3 said:
Working perfectly. The system is rooted
How do I check if the device is booting with this kernel?
Thanks a ton btw!
Click to expand...
Click to collapse
after flashing the kernel using the given command did the device start and boot up into android OS?
DooMLoRD said:
after flashing the kernel using the given command did the device start and boot up into android OS?
Click to expand...
Click to collapse
Are you asking if it booted successfully after flashing? Yes it did.
But, in the Kernel Version it still says : "[email protected] #1". Wouldn't it be different if you recompiled it?
Pwng3 said:
Are you asking if it booted successfully after flashing? Yes it did.
But, in the Kernel Version it still says : "[email protected] #1". Wouldn't it be different if you recompiled it?
Click to expand...
Click to collapse
thats good enough...
the kernel is from stock kernel.sin, as no kernel sources are available at the moment i cannot do a fresh clean compile...
anyways i am updating the 1st post with the info that the kernel is tested on a device and it works
DooMLoRD said:
thats good enough...
the kernel is from stock kernel.sin, as no kernel sources are available at the moment i cannot do a fresh clean compile...
anyways i am updating the 1st post with the info that the kernel is tested on a device and it works
Click to expand...
Click to collapse
Please go ahead
Waiting for Sony to release the sources so that we can lay our hands on our very own DoomKernel
Pwng3 said:
Please go ahead
Waiting for Sony to release the sources so that we can lay our hands on our very own DoomKernel
Click to expand...
Click to collapse
i wont be working on custom kernels for Xperia P, Sola & U as i dont have those devices and in anycase i dont have time to work on them...
honestly i would have LOVED to, but due to lack of time i will be barely able to support the existing devices i have (ARC, PLAY, S)... so i dont want to take up additional responsibilities when i know that i wont have time to work on those devices as of now...
DooMLoRD said:
great so can u confirm that the device boots with this kernel? also does the system get rooted?
P.S.: recovery is currently NOT integrated
Click to expand...
Click to collapse
yes, the system is rooted great job!! thx
waiting for integrated recovery with DoomKernel+OC
DooMLoRD said:
i wont be working on custom kernels for Xperia P, Sola & U as i dont have those devices and in anycase i dont have time to work on them...
honestly i would have LOVED to, but due to lack of time i will be barely able to support the existing devices i have (ARC, PLAY, S)... so i dont want to take up additional responsibilities when i know that i wont have time to work on those devices as of now...
Click to expand...
Click to collapse
Ouch! That's a bummer
I was really looking forward to powering up my phone with a sexy Kernel...
Goodluck nevertheless, have fun in IIMA
Tapatalked from Xperia U
it works. the phone is rooted now, but keep in mind to do a backup of your sms/whatsapp/app, before flash this kernel.
I hear sometimes, a strange "tic tic" from the speaker, never heard before flashing doomkernel.
I will keep testing this
Thank you man!
Pwng3 said:
Ouch! That's a bummer
I was really looking forward to powering up my phone with a sexy Kernel...
Goodluck nevertheless, have fun in IIMA
Tapatalked from Xperia U
Click to expand...
Click to collapse
i know a few devs who are interested in creating kernel for this device... so dont worry u guys will get custom kernel once sources are released!
Thanks for you work :-D
Envoyer depuis mon Nozomi avec Tapatalk
dimostar said:
it works. the phone is rooted now, but keep in mind to do a backup of your sms/whatsapp/app, before flash this kernel.
I hear sometimes, a strange "tic tic" from the speaker, never heard before flashing doomkernel.
I will keep testing this
Thank you man!
Click to expand...
Click to collapse
I also hear those "tic tic" when closing or opening apps sometimes, im on stock ROM
pel.89 said:
I also hear those "tic tic" when closing or opening apps sometimes, im on stock ROM
Click to expand...
Click to collapse
I had the same problem even when I was on the stock Kernel. Very rarely though. So I'm pretty sure that there is nothing wrong with the Kernel posted by DoomLord.
DoomKernel perhaps?
it's was disappointing...DooMKernel is very good kernel...
doesnt work for me
type all in, but said that i need root access
edit: ok...i got it
XDA_Bruno said:
it's was disappointing...DooMKernel is very good kernel...
Click to expand...
Click to collapse
I understand, but you shouldn't worry, there are many devs interested in this phone.
I being one of them will be quick to create custom kernel once I get my device (month or 2) and I will be working in the FreeXperia team to bring CM9 to this device
Although, I wouldn't say I am as good as DooMLoRD, I'm sure you will enjoy the work of me and other developers
Keiran
Sent from my Xperia Play using Tapatalk 2
Please knowledgeable people help me in getting at the root smartphone. I have tried every possible way. It was the ADB can not access, so this installation method will not work. Looking for a digital computer, but it is not under our device.
Click to expand...
Click to collapse
I and SergioPoverony from 4pda . ru build fully worked CWM 6.0.2.1 for Alcatel 993D!
Unpack CWM 6.0.1.2_final_install.zip to root folder and start "install-recovery-windows.bat"
Download:View attachment 1509133
For restore original recovery download: View attachment recovery_orig.zip
Afer install any root.zip for CWM! GoodLuck!
Original post on Russian forum: 4pda.ru
beeline09 said:
Please knowledgeable people help me in getting at the root smartphone. I have tried every possible way. It was the ADB can not access, so this installation method will not work. Looking for a digital computer, but it is not under our device.
Click to expand...
Click to collapse
I've got great news for you !
I have successfully rooted the device with this tool: http://forum.xda-developers.com/attachment.php?attachmentid=1343515&d=1348245161
Just follow the instructions, that the program says!
Credits goes to: Bin4ry
Original thread can be found here: http://forum.xda-developers.com/showthread.php?t=1886460
{
"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"
}
Root, flash player, cwm recovery.
qltsar said:
I've got great news for you !
I have successfully rooted the device with this tool: http://forum.xda-developers.com/attachment.php?attachmentid=1343515&d=1348245161
Just follow the instructions, that the program says!
Credits goes to: Bin4ry
Original thread can be found here: http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
To root, I need to install some drives in Pc.
There is flash player, and cwm recovery, for this smartphone.
Thanks for the answers
lmt399 said:
To root, I need to install some drives in Pc.
There is flash player, and cwm recovery, for this smartphone.
Thanks for the answers
Click to expand...
Click to collapse
There is no any customized CWM yet, you can download flashplayer manually from the internet, just try to google it .
The drivers included at the phone's flasher tool, in the One Touch Upgrade Q, or you can install Android Manager. Both of them have the necessary drivers.
qltsar said:
There is no any customized CWM yet, you can download flashplayer manually from the internet, just try to google it .
The drivers included at the phone's flasher tool, in the One Touch Upgrade Q, or you can install Android Manager. Both of them have the necessary drivers.
Click to expand...
Click to collapse
Ok thanks for the reply.
I bought one, should arrive tomorrow.
Keep the thread alive.
CWM recovery PLEASE...
qltsar said:
I've got great news for you !
I have successfully rooted the device with this tool: http://forum.xda-developers.com/attachment.php?attachmentid=1343515&d=1348245161
Just follow the instructions, that the program says!
Credits goes to: Bin4ry
Original thread can be found here: http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
Phone rooted successfully.
Any news about, CWM recovery or costum room.
qltsar said:
I've got great news for you !
I have successfully rooted the device with this tool: http://forum.xda-developers.com/attachment.php?attachmentid=1343515&d=1348245161
Just follow the instructions, that the program says!
Credits goes to: Bin4ry
Original thread can be found here: http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
Thank you used this on my OT-997D and i have root acces thanks
CWM recovery?
Klaasv00k said:
Thank you used this on my OT-997D and i have root acces thanks
Click to expand...
Click to collapse
Who could receive CWM recovery on Alcatel One Touch 993d -997? I ask to help with it .
72angel86 said:
Who could receive CWM recovery on Alcatel One Touch 993d -997? I ask to help with it .
Click to expand...
Click to collapse
I've tried to make it, but it seems to be there are some problems...I can get a rootshell, but the display can't work.
The OT-997 is another fail for me. I cannot make the communication between SP Flashtool and the device. It seems that the scatter file is incorrect, but i don't know how to correct it. If there is someone who has a little experience with ZTE V970 please help me with this, because that model has the same MTK chipset.
qltsar said:
I've tried to make it, but it seems to be there are some problems...I can get a rootshell, but the display can't work.
The OT-997 is another fail for me. I cannot make the communication between SP Flashtool and the device. It seems that the scatter file is incorrect, but i don't know how to correct it. If there is someone who has a little experience with ZTE V970 please help me with this, because that model has the same MTK chipset.
Click to expand...
Click to collapse
I do not know much about cmw recovery but used it on other phones to flash a custom ROM
I have used the method described here to see if I could root my phone
it worked and now I can install AdFree to block advertising
I do not have advertising on my phone now
because the OT-997D is a brand new phone release date 10/10/2012
I do not think there is already a custom ROM for the phone
for CWM Recovery
try http://builder.clockworkmod.com/
you need to dump your stock recovery.img
magikstar said:
for CWM Recovery
try http://builder.clockworkmod.com/
you need to dump your stock recovery.img
Click to expand...
Click to collapse
Do you think, i didn't tried that solution? The recovery-s that i built, couldn't show anything on the screen. It seemes that the device has a specalized framebuffer to initialize the display. I've also tried to port a CWM from a 7227A device, but I was facing the same problems.
CWM
qltsar said:
Do you think, i didn't tried that solution? The recovery-s that i built, couldn't show anything on the screen. It seemes that the device has a specalized framebuffer to initialize the display. I've also tried to port a CWM from a 7227A device, but I was facing the same problems.
Click to expand...
Click to collapse
Sorry for my english, translate through Google. I am a Russian-speaking. Here is a partition table for the Alcatel OT-993D:
Code:
/dev/block/mmcblk0p1 qcsblhd_cfgdata.mbn
/dev/block/mmcblk0p2 qcsbl.mbn
/dev/block/mmcblk0p3 /FAT vfat AMSS.MBN AMSSHD.MBN
/dev/block/mmcblk0p5 OEMSBL.MBN
/dev/block/mmcblk0p6 /APPSBL emmc EMMCBOOT.MBN
/dev/block/mmcblk0p7
/dev/block/mmcblk0p8 /boot emmc boot.img
/dev/block/mmcblk0p9
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
/dev/block/mmcblk0p12 info about imei, FW version, boot & recovery version
/dev/block/mmcblk0p13 /system ext4 system
/dev/block/mmcblk0p14 /data ext4 data
/dev/block/mmcblk0p15 /custpack ext4 custom
/dev/block/mmcblk0p16 /cache ext4 cache
/dev/block/mmcblk0p17 /recovery emmc recovery.img
/dev/block/mmcblk0p18 /misc emmc misc
/dev/block/mmcblk0p19 /secro emmc secro
/dev/block/mmcblk0p20
/dev/block/mmcblk0p21 /emmc vfat userdata
/dev/block/mmcblk1p1 /dev/block/mmcblk1p2 /sdcard vfat ???????
Managed by busybox dd command to copy the recovery partition. Then I do not know what to do. I hope I helped somewhat. Really want CWM to our phone. Let's get together sometime and try to port CWM for this circuit?
Auto-capitalization (Messages)
Anyone else experiencing the auto-capitalization problem whenever you type in messages. Did you find any solution to this?
What?
spaces27 said:
Anyone else experiencing the auto-capitalization problem whenever you type in messages. Did you find any solution to this?
Click to expand...
Click to collapse
I do not understand. Can you explain to another?
beeline09 said:
I do not understand. Can you explain to another?
Click to expand...
Click to collapse
Hello beeline09.
Can I get the battery mod that put you in the Russian forum.
http://4pda.ru/forum/index.php?showtopic=371270&st=1600
post#1619
Thank you very much
Yes
lmt399 said:
Hello beeline09.
Can I get the battery mod that put you in the Russian forum.
post#1619
Thank you very much
Click to expand...
Click to collapse
Yes, of course! Proceed as indicated in the instructions and you will have a battery
Upload your battery mod file - systemui.apk
beeline09 said:
Yes, of course! Proceed as indicated in the instructions and you will have a battery
Click to expand...
Click to collapse
yes, but what I needed was your battery mod file - systemui.apk.
Upload to this thread.
thank you :fingers-crossed:
CWM really working on Alctatel OT-993D
qltsar said:
Do you think, i didn't tried that solution? The recovery-s that i built, couldn't show anything on the screen. It seemes that the device has a specalized framebuffer to initialize the display. I've also tried to port a CWM from a 7227A device, but I was facing the same problems.
Click to expand...
Click to collapse
We already have a working CWM. Link: on russian site 4 pda ru
beeline09 said:
We already have a working CWM. Link: on russian site 4 pda ru
Click to expand...
Click to collapse
Good job.
{
"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"
}
Requirements:
Flashtool 0.9.13 by @Androxyde
XZDualRecovery 2.7.43 BETA or newer.
Current rooted FW version: 14.1.B.1.532 or 14.1.B.2.257.
Special features:
SuperSU integrated in system, FULL ROOT!
XZDualRecovery 2.7.75 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
init.d support (read how to enable)
For both locked and unlocked bootloaders!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
If you are unable to download torrent files directly, have http://zbigz.com/ do it for you!
How to update to 14.2.A.0.290:
Files:
For C6802: Download C6802_14.2.A.0.290.flashable.zip (Bittorrent: 842MB) and C6802_14.2.A.0.290_Stripped.ftf (21MB)
For C6806: Download C6806_14.2.A.0.290.flashable.zip (Bittorrent: 815MB) and C6806_14.2.A.0.290_Stripped.ftf (21MB)
For C6833: Download C6833_14.2.A.0.290.flashable.zip (Bittorrent: 760MB) and C6833_14.2.A.0.290_Stripped.ftf (21MB)
Save them somewhere you remember;
Due to a little bug inside the updater-script, you need to follow the guide in this post to make sure flashing it works OK. (Only if you downloaded the older version)
Put 'C68XX_14.2.A.0.290.flashable.zip' on (the external) SDcard1;
Put 'C68XX_14.2.A.0.290_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in TWRP and don't forget to backup the contents of 'SDCard' (the internal storage!);
Install XZDualRecovery 2.7.74 or newer from PC.
In TWRP -> Wipe -> advanced Wipe Tick/Check:
Dalvik-Cache
System
Cache
Data
Then 'Swipe to Right' to make it happen and go back to the TWRP home screen;
Flash 'C68XX_14.2.A.0.290.flashable.zip' in TWRP;
NOTE: do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C68XX_14.2.A.0.290_Stripped.ftf';
Now reboot to system;
Once you get to the language select screen, reboot to TWRP (no need to finish the guide);
Restore the backup of DATA only, when done go back to the TWRP home screen;
In TWRP -> Wipe -> advanced Wipe Tick/Check Dalvik-cache;
Reboot to system.
The first boot will be slow and after a long wait at the boot animation you will see Android start optimizing the apps on your phone.
Video Guide:
NOTE: This guide is based on an older guide for the Xperia Z1 which has since been updated a few times, but it will give you a general idea.
shem2409 said:
Click to expand...
Click to collapse
Enjoy! :fingers-crossed:
Known XZDualRecovery Issues:
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore any JB 4.2.2 FTF using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
Install XZDualRecovery and then try to update again using TWRP.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /sdcard1/XZDualRecovery, pack them up and send them to me or attach them to your bug report.
Thank you
XDA:DevDB Information
[STOCK][4.3] Update to 14.2.A.0.290 [Root & XZDR][LB/UB], a ROM for the Sony Xperia Z Ultra
Contributors
[NUT]
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.1.B.1.532 or 14.1.B.2.257
Based On: STOCK
Version Information
Status: Stable
Stable Release Date: 2014-01-18
Created 2014-01-16
Last Updated 2014-01-21
Tips and Tricks
Easy switching between locked and unlocked bootloader states!
NOTE: USE TWRP ONLY for this guide.
NOTE 2: You NEED to have XZDualRecovery 2.7.43 or higher to make this work.
Create a backup, including the Trim Area (TA!)
Unlock your bootloader
Restore backup without TA
Create a new backup of your UNLOCKED TA
Restore the previous TA backup to relock your phone.
Done :good:
Now you can switch between locked and unlocked bootloaders quick and painless: no more system wipes and you can basically do whatever you want
How to enable init.d support:
Open a filemanager app and navigate to the location where the XZDualRecovery folder is located and go in to it. Open XZDR.prop as a text file and set dr.initd.active to true.
NOTE: For this ROM it means the init.d script called 99SuperSUDaemon will kick in to action, so it's best to disable (by setting chmod 644) /system/etc/install-recovery.sh for the time being or to clear it's contents.
Done
Downgrading to a 4.2 ROM:
Download C6833_14.1.B.1.532_[NUT].ftf (Bittorrent: 760MB) and flash it using FlashTool. I've also added the FTF to the downloads page on the DevDB tab, this will allow straight downloads as well.
This FTF will allow you to downgrade to .532 without loss of your IMEI :good:
ROM Status: STABLE
Update 1:
C6802 ROM uploaded and seeding.
Update 2:
C6833 ROM uploaded and seeding.
Update 3:
C6806 ROM now uploading, FTF and torrent file links have been updated.
Update 4:
C6806 ROM uploaded and seeding.
Update 5:
A little bug has been discovered in the updater-script. To be able to flash the one you possibly have downloaded already, follow the instructions in this post to get it to work properly!
I will be updating the packages soon, in the mean time I have updated the OP guide to include this small fix.
Update 6:
Removed the files from the bit-torrent seeder. I'm currently uploading them again now. It will probably take about 30 minutes to finish that, will update again once completed and seeding again.
If you have already downloaded the package, make sure to read 'Update 5' with details on that how to fix yours.
Update 7:
Files have been replaced on the seeder box. There is no need to re-download them if you follow the guide pointed to by 'Update 5'.
Enjoy again!
Good work @[NUT] :thumbup:
sent from my monx®dified 6802 using Tapatalk
290 is it lte For C6833
Sent from my C6833 using XDA Premium 4 mobile app
jpeps said:
290 is it lte For C6833
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have lte now, then that will be the same for this package
Yet another ROM! Great work, NUT!
Anyone who has tested it please do let me know. If you are unable to post here because you just registered on xda, feel free to PM me your experience!
Anyone who can upload both the c6802 files anywhere else as cant download from given links.
techpal said:
Anyone who can upload both the c6802 files anywhere else as cant download from given links.
Click to expand...
Click to collapse
Why?
Failed
Tried a few times to flash C6833_14.2.A.0.290.flashable.zip in TWRP, but each time it failed in the final step:
Code:
set_perm: some changes failed
E:Error in /sdcard/C6833_14.2.A.0.290.flashable.zip
(status 7)
So I decided to try the flashable zip from jackie099's thread, and that one was successful.
Djezpur said:
Tried a few times to flash C6833_14.2.A.0.290.flashable.zip in TWRP, but each time it failed in the final step:
Code:
set_perm: some changes failed
E:Error in /sdcard/C6833_14.2.A.0.290.flashable.zip
(status 7)
So I decided to try the flashable zip from jackie099's thread, and that one was successful.
Click to expand...
Click to collapse
Ah frack, because of this report, I just rechecked my edify script, and even though it was correct typo wise, it is trying to set permissions on a file which no longer exists in the package.
I'll redo the packages soon. Packages have been updated. If you have one downloaded already, follow this little guide to fix yours!
In the mean time, open the flashable ZIP in winzip or winrar, extract META-INF/com/google/android/updater-script
and remove this line:
Code:
set_perm(0, 0, 0644, "/system/bin/ramdisk.stock.cpio.lzma");
Put the updater-script back inside the zip, updating the one there. It should make it flash OK from there on.
Thanks for the report!
thanks for all your hard work! however, torrents do not download (understand dependent on other servers etc) hope someone can post these (C6833) Thanks
mac231us said:
thanks for all your hard work! however, torrents do not download (understand dependent on other servers etc) hope someone can post these (C6833) Thanks
Click to expand...
Click to collapse
Then your ISP is blocking them... or you are getting blocked by mine
Try http://zbigz.com to download the torrent file, they turn it in to a straight download for you.
[NUT] said:
Thanks for the report!
Click to expand...
Click to collapse
And thank you for providing a way to root .290 with a locked bootloader. :good:
Djezpur said:
And thank you for providing a way to root .290 with a locked bootloader. :good:
Click to expand...
Click to collapse
So, you fixed and flashed it and it's confirmed working?
I need that confirmation to change the Post 3 status
[NUT] said:
So, you fixed and flashed it and it's confirmed working?
I need that confirmation to change the Post 3 status
Click to expand...
Click to collapse
Yep, all is good now!
sorry for being a noob, but how to flash the stripped ftf part?
im thinking of using flashtool but im stuck on waiting for flashmode, saying i should press back button which we dont have. any help?
im stuck here
thanks before
Justin^Tan said:
sorry for being a noob, but how to flash the stripped ftf part?
im thinking of using flashtool but im stuck on waiting for flashmode, saying i should press back button which we dont have. any help?
im stuck here
thanks before
Click to expand...
Click to collapse
Set up flashtool to where it asks you to connect your phone:
Turn off your mobile, then hold Volume down while connecting your usb cable. It will then start flashing.
Holding volume up will put your device in to fastboot mode, FYI
ahh, volume down lol. great, that did the rick
thanks a lot NUT! appreciate your job hehe. great work
oh right, i still have the notification of OTA update to 290 after i flashing your ROM. is there any way to clear it?
Since vivo developers doesn't make any efforts to make the sources open, so, it is obvious that some functions might not work
Warning !!! Your Warranty is now void.
If You understand the risks and still want to play with your phone, go ahead,
No one will stop you, DUDE!!!
Downloads :-
Download TWRP recovery for vivo y51l
Latest :- TWRP 3.21. OTG fixed :- https://goo.gl/BUpUhc
twrp_3.1.1_for_vivo_y51l
twrp_3.2.1_for_vivo_y51l
TWRP_3.2.1-0-vivo-y51l-y21lkernel (Warning!!! flash this version only if you have flashed y21l kernel to enable root.)
Firmware Update & Bootloader unlock :-
To Install TWRP Recovery, first , we’ve to unlock bootloader of vivo y51l.
So, Follow the steps:-
Download The Latest firmware (PD1510F_EX_C_2.6.13) available from here
Google Drive Link
)
How To Flash :-
https://www.youtube.com/watch?v=IQEQ5jD269k
Now flash the firmware you downloaded above.
If you got Invalid IMEI MEID Error, See this thread.
Now You have flashed the latest available firmware and its time to unlock bootloader and flash twrp to your vivo y51l.
Now Again (‘,‘), follow the instructions in this guide to unlock y51l bootloader
Flash TWRP in vivo y51l :-
Connect Your vivo y51l to pc with usb debugging enabled
Now Open Open Command Prompt or Terminal and type
adb reboot bootloaderor
sudo adb reboot bootloader (If u r using linux)
{
"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"
}
Now your phone will reboot into fastboot mode
Now download the TWRP Recovery for vivo y51l from the download section (No need if u’ve already downloaded)
Now extracts the downloaded zip file and You’ll get a file named twrp_3.1.1.img
Now Type
fastboot flash recovery twrp_3.1.1.imgor
sudo fastboot flash recovery twrp_3.1.1..img (If u r using linux)
Sorry For the excessive use of word “NOW”
That’s it. Your Vivo Y51L is now Running one of the best & latest custom recovery available on Planet EARTH.
Credits : Me, Me & Me
YouTube Video on the same :
https://www.youtube.com/watch?v=cA8QrAXsINc
Bingo......
UNOFFICIAL CM 12.1 for Vivo y51l is out, Have a look :
https://www.youtube.com/watch?v=2uSqIYiqXU4
Original Thread Here
Want to make more out of your Vivo Phone?
Sign the Petition to release kernel sources :
http://chn.ge/2E2N70w
Great job...bro
Hey bro, did you tried to flash supersu.zip?
shahnawaz_sheikh said:
Hey bro, did you tried to flash supersu.zip?
Click to expand...
Click to collapse
yes, flashed it, but there's a code in the kernel which prevents su binary execution.
And for the thumbnail you provided :
You can use the fastboot mode on vivo to only flash
recovery, boot command is not supprted.
Naveen Singh said:
yes, flashed it, but there's a code in the kernel which prevents su binary execution.
And for the thumbnail you provided :
You can use the fastboot mode on vivo to only flash
recovery, boot command is not supprted.
Click to expand...
Click to collapse
But that doesn't mean we cant make custom roms right??
shahnawaz_sheikh said:
But that doesn't mean we cant make custom roms right??
Click to expand...
Click to collapse
Yes, we can make custom roms,
i've ported miui 8 with lots of hardware issues,
But the problem is kernel source.
Because we cant build a kernel without source.
Bro did you have any problems In your phone...after booting.i need to upgrfforto 2.6.13 version in my vivo y51L...may you tell me Plz.. If you had issues or problems.if you had any issues just tell me i will decide to root my vivo y51l
gokulbuddy Sp said:
Bro did you have any problems In your phone...after booting.i need to upgrfforto 2.6.13 version in my vivo y51L...may you tell me Plz.. If you had issues or problems.if you had any issues just tell me i will decide to root my vivo y51l
Click to expand...
Click to collapse
No problems,
If you are flashing using qfil then choose PD1510F..........no_qcn.xml file for flashing
Never choose to flash qcn otherwise you will lose your imei and qcn stuffs
How to find that qfil bro..What is that
IOS custom rom
Please IOS Custom rom for Micromax q385
shahnawaz_sheikh said:
Hey bro, did you tried to flash supersu.zip?
Click to expand...
Click to collapse
yess, I need to flash it on TWRP !
---------- Post added at 03:33 PM ---------- Previous post was at 03:22 PM ----------
how to flash binary superSU or update superSU.zip on twrp 3.1.1...plz
jabirfan said:
yess, I need to flash it on TWRP !
---------- Post added at 03:33 PM ---------- Previous post was at 03:22 PM ----------
how to flash binary superSU or update superSU.zip on twrp 3.1.1...plz
Click to expand...
Click to collapse
Just flash it in twrp (click install button) man
Bro can you tell me How to use qfill? I dont know well about that....if you help me i will get better idea.......the qfil is a flash driver am i right or not.if it is right... how to use?
gokulbuddy Sp said:
Bro can you tell me How to use qfill? I dont know well about that....if you help me i will get better idea.......the qfil is a flash driver am i right or not.if it is right... how to use?
Click to expand...
Click to collapse
Qfil is flasht tool by Qualcomm for devices with Qualcomm chipsets. I will post a qfil tutorial soon.
Kepp coming....
Ok i will be wait...thanks for this comitment..
Naveen Singh said:
Just flash it in twrp (click install button) man
Click to expand...
Click to collapse
I have installed update.zip file, but why binary is not installed and always fail rooting
Unlocking Bootloader VIVO Y51L
..
how to solved this ?? im used windows 10 professional... help
Reza Adrian said:
..
how to solved this ?? im used windows 10 professional... help
Click to expand...
Click to collapse
pastikan saja semua driver sudah terinstall kemudian install adb interface dengan cara manual dan lihat pemberitahuannya.
Jika belum paham silahkan lihat tutorialnya di google
jabirfan said:
I have installed update.zip file, but why binary is not installed and always fail rooting
Click to expand...
Click to collapse
Root permission isn't available for vivo y51l yet
The reason is unsupported kernel. Hope u understand.
Reza Adrian said:
..
how to solved this ?? im used windows 10 professional... help
Click to expand...
Click to collapse
Is oem unlock enabled from developer settings?