Related
As there is now an official version of CWM Recovery I updated this thread now. Thanks to everyone who used my version and helped me. I will keep on what I'm doing and maybe there will be other interesting things I will release.
The official CWM Recovery by Koush can be downloaded here:
Images to flash via fastboot
touch-version: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.7-mako.img
nontouch-version: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-mako.img
Flashable zips
touch-version: https://www.mediafire.com/?nx826v1jo0bdqdj
nontouch-version: https://www.mediafire.com/?69kmvtcvgooc0gv
For the fastboot images:
You can try this out and boot it via
Code:
fastboot boot recovery-clockwork(-touch)-6.0.4.7-mako.img
(only Android 4.2.X)
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery-clockwork(-touch)-6.0.4.7-mako.img
(Android 4.3 and above)
If you want to flash it you can use
Code:
fastboot flash recovery recovery-clockwork(-touch)-6.0.4.7-mako.img
If you have the touch-version use this commands without '(' and ')' but with its content.
If you have the nontouch-version use this commands without '(' and ')' and its content-
Outdated as all new recoveries already provide this function.
I also want to present you my revert recovery disabler.
As you know if you flash CWM on Nexus 4 it reverts back to the stock recovery. This patch prevents this. This is not needed at the moment for CWM as CWM offers the possibly to disable the revert by itself.
You can download my revert recovery disabler here: http://www.mediafire.com/?78fkhdh5icz3zdg
This disabler is compatible with mskip's toolkit (uses the same methode).
To use it boot in CWM recovery and flash this as a zip.
If you want to restore the default option and make your Nexus 4 reverting back to the stock recovery you can flash the enabler: http://www.mediafire.com/?19enww985e2gpnc
Thanks to:
Stryder5 providing some information
Kstarz for some testing and providing information
mskip for his toolkit and giving me the idea to do this
pankaj88 for his sample update zip
Old thread said:
I just want to release my CWM Touch Recovery for the Nexus 4.
This version also allows to flash zips from internal storage (and hopefully other storage related stuff).
If you want to you can download it here: http://www.mediafire.com/?f9b9av06ui5vcdm (UPDATED 11/16/2012)
Using it is at your own risk!
Please test it first via
Code:
fastboot boot cwm-recovery-mako.img
Flashing is not supported at the moment as secured boot prevents from booting flashed recovery. Please note that you need an unlocked bootloader.
For reverting back to original recovery use this one: http://www.mediafire.com/?57zmq7yw089gcr8 (not needed at the moment as only booted recovery works at the moment)
Thanks to:
Stryder5 for testing and providing some information
Kstarz for testing and providing some information
Also thanks to Koush for creating CWM Recovery and to the other devs for Nexus 4 making it a really good device.
If you have any questions ask below. I will rework this post later the day.
Click to expand...
Click to collapse
To clarify, I can confirm the boot method will allow you to boot the recovery and flash a zip file. I did not attempt to flash this as my recovery yet.
---------- Post added at 12:53 AM ---------- Previous post was at 12:21 AM ----------
I tried to flash the recovery instead of booting from it, but that doesn't work. I ran the command:
Code:
fastboot flash recovery cwm-recovery-mako.img
When I try to boot into recovery after that, it'll show the Google logo twice, then proceed with the regular boot.
I think this is because Secure Boot is still enabled.
Same thing here..recovery will not stick if flashed
Sent from my Nexus 4
good news! https://plus.google.com/u/0/103583939320326217147/posts/CzstapsDpYf
fkrone said:
I just want to release my CWM Touch Recovery for the Nexus 4.
This version also allows to flash zips from internal storage (and hopefully other storage related stuff).
If you want to you can download it here: http://www.mediafire.com/?f9b9av06ui5vcdm (more mirrors will be added soon)
Using it is at your own risk!
Please test it first via
Code:
fastboot boot cwm-recovery-mako.img
Flashing is not supported at the moment as secured boot prevents from booting flashed recovery. Please note that you need an unlocked bootloader.
For reverting back to original recovery use this one: http://www.mediafire.com/?57zmq7yw089gcr8 (not needed at the moment as only booted recovery works at the moment)
Thanks to my tester Stryder5.
Also thanks to Koush for creating CWM Recovery and to the other devs for Nexus 4 making it a really good device.
If you have any questions ask below. I will rework this post later the day.
Click to expand...
Click to collapse
What RAMDISK load address are you using? 0x81200000?
Thanks to the tip by Stryder5, I have updated my rooting guide with instructions for rooting via CWM, linking to this thread for the recovery and providing the due credit. =)
g33k3r said:
What RAMDISK load address are you using? 0x81200000?
Click to expand...
Click to collapse
If I could I would provide you that information but as I only used the CWM's online builder I can't tell you that. If you need some information you can pm me
To all: As there is a new update in the sources I am currently syncing the sources and building an new version. Furthermore I am working on a possibility to make the CWM permanent (and easy to do so even without root; I know already what I have to do).
fkrone said:
If I could I would provide you that information but as I only used the CWM's online builder I can't tell you that. If you need some information you can pm me
To all: As there is a new update in the sources I am currently syncing the sources and building an new version. Furthermore I am working on a possibility to make the CWM permanent (and easy to do so even without root; I know already what I have to do).
Click to expand...
Click to collapse
Looking forward to it!
Sent from my Nexus 4 using xda app-developers app
does anyone actually build cwm these days?
Sweet!! So our Nexus 4 is codenamed "MAKO?"
DaX05 said:
Sweet!! So our Nexus 4 is codenamed "MAKO?"
Click to expand...
Click to collapse
The hardware is calles mako, the software itself has the codename occam. As of my building methode it was automatically called mako
fkrone said:
The hardware is calles mako, the software itself has the codename occam. As of my building methode it was automatically called mako
Click to expand...
Click to collapse
Hey do you mind if I put this recovery in the Toolkit for now until koush has released the official cwm?
Is it touch or non touch? What version is it?
Mark.
mskip said:
Hey do you mind if I put this recovery in the Toolkit for now until koush has released the official cwm?
Is it touch or non touch? What version is it?
Mark.
Click to expand...
Click to collapse
No problem at all. Just give credits and use it. This is a touch recovery.
If koush will release CWM for Nexus 4 it won't be different to this (except he changes some sources).
fkrone said:
No problem at all. Just give credits and use it. This is a touch recovery.
If koush will release CWM for Nexus 4 it won't be different to this (except he changes some sources).
Click to expand...
Click to collapse
Thanks and of course
What version is it? V6.0.1.5?
Mark.
mskip said:
Thanks and of course
What version is it? V6.0.1.5?
Mark.
Click to expand...
Click to collapse
As I built it this afternoon (GMT+1) it is V6.0.1.5 with the latest bugfix which was released today.
Man I can't wait to see some custom ROM's outta here. The phone is sweet and snappy but I've had a few problems that I'm not sure if they're hardware or software related. Quadrant scores are around 4400-4900, the phone rings hot and I'm getting the worst speed test results. Like I get 11-18 MBS on my gs2 and I'm getting like 2-3mbs now. I got two weeks before I can return it so I hope it just needs to stettle. Anyhoo. Good luck guys!
Sent from my Nexus 4 using XDA Premium HD app
Link to the new recovery (6.0.1.6-mako)
But assuming that I flashed it correctly with Rom Manager and fastboot, it isn't working, it didn't matter which way i flashed it.
Arasthel said:
Link to the new recovery (6.0.1.6-mako)
But assuming that I flashed it correctly with Rom Manager and fastboot, it isn't working, it didn't matter which way i flashed it.
Click to expand...
Click to collapse
Flashing does not work at the moment. Only booting via fastboot even with official CWM Recovery.
fkrone said:
Flashing does not work at the moment. Only booting via fastboot even with official CWM Recovery.
Click to expand...
Click to collapse
Sorry, I misunderstood you. I thought this bugfix would allow us to flash the recovery in our devices, then I realized that the bugfix was what let us boot it, as you said a few messages back. Anyway, there you have the official build link.
Can somebody please explain, in simple terms, why we can't flash this permanently yet? What do we need to enable us to flash it permanently?
ClockworkMod Recovery (6.0.5.1) Open Bump Edition for LG G Pad 8.3 v500. This custom recovery installation package is for v500 models only. Built from source on 2014-12-13 by Jenkins. This version of CWM 6.0.5.1 has been "bumped" so that loki tool is not required.
Installation: Flash zip file with any custom recovery and reboot into updated CWM recovery.
v500-CWM-6.0.5.1-20141213-recovery-bumped-signed.zip
MD5: 8c8593fc0fb8039949c0f06d48d97e4f
Note: An advantage to using the official CWM recovery with CM 11 is that the CWM recovery can be automatically updated with the CM Update tool, if enabled in the CM 11 developer options.
Manual Installation (first time installing custom recovery):
1) Gain root permission (ie; with Stumproot) and install SuperSU and Busybox.
2) Install Terminal Emulator or use ADB for opening up a shell (this example is using ADB).
Note: If using Terminal Emulator, make sure root access is given via SuperSU.
3) Download CWM installation zip file from the link above and manually extract it.
4) Copy recovery.img (contained in the CWM installation zip file from step #3) to /data/local/tmp on your LG G Pad 8.3 v500 tablet with either ADB or a root explorer application and install with "dd" command.
Code:
adb push recovery.img /data/local/tmp/
adb shell
su
cd /data/local/tmp
ls recovery.img
dd if=recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
is this the touch version?
This is the latest official swipe version. It's not full touch.
Deltadroid said:
This is the latest official swipe version. It's not full touch.
Click to expand...
Click to collapse
are there any plans to port the touch version to the g pad?
Not at the moment. This recovery was taken from the official nightly builds. I did not personally build it. I have only "bumped" the image and packaged it.
only bumped roms or kernels works with bumped recoverys? what happens if i flash a normal rom?
auleu said:
only bumped roms or kernels works with bumped recoverys? what happens if i flash a normal rom?
Click to expand...
Click to collapse
Any rom or kernel can be installed with a bumped recovery. Although, some ROMs require that your aboot partition is from 4.2.2 so that loki will work so that the kernel can be installed (which has nothing to do with the recovery).
Deltadroid said:
Any rom or kernel can be installed with a bumped recovery. Although, some ROMs require that your aboot partition is from 4.2.2 so that loki will work so that the kernel can be installed (which has nothing to do with the recovery).
Click to expand...
Click to collapse
Installed this recovery following the instructions :
adb reboot recovery : my tablet didn't reboot to recovery but to system
then I boot into recovery using Titanium Backup (there's an option to boot into recovery in the menu)
I tried to install latest official CM12 nightly : error
tried with latest AOSP 5.1 too, same error
So I tried to toggle Loki in the CWM settings , same results.
Now I can't boot into system nor recovery : "Security Error"
Looks like I'm good to flash once again the stock rom...
Any tips to be able to install CM12 or AOSP 5.1 ?
Phenom2 said:
Installed this recovery following the instructions :
adb reboot recovery : my tablet didn't reboot to recovery but to system
then I boot into recovery using Titanium Backup (there's an option to boot into recovery in the menu)
I tried to install latest official CM12 nightly : error
tried with latest AOSP 5.1 too, same error
So I tried to toggle Loki in the CWM settings , same results.
Now I can't boot into system nor recovery : "Security Error"
Looks like I'm good to flash once again the stock rom...
Any tips to be able to install CM12 or AOSP 5.1 ?
Click to expand...
Click to collapse
When you typed "adb reboot recovery", make sure you unplug the usb cable or it will not reboot into recovery.. this occurs with all versions of CWM.
When you install a ROM, make sure that your aboot partition is loki exploitable (from 4.2.2) or it will not be able to install the kernel. Most ROMs still use the loki method to install the kernel, which still requires the older aboot.
Deltadroid said:
When you typed "adb reboot recovery", make sure you unplug the usb cable or it will not reboot into recovery.. this occurs with all versions of CWM.
When you install a ROM, make sure that your aboot partition is loki exploitable (from 4.2.2) or it will not be able to install the kernel. Most ROMs still use the loki method to install the kernel, which still requires the older aboot.
Click to expand...
Click to collapse
Ok, so I should flash the first stock rom before trying to install a recovery right ?
- Flash 1st stock rom
- Get root (I use towelroot)
- Install recovery with cmd
- Boot recovery and flash rom + gapps
Right ? (edit : OK, I managed to install AOSP 5.1 with theses instructions coming from stock V50010B)
I understood that there's 2 major exploit, loki and bumb.
4.4 = bumb only
4.2.2 = both ?
Isn't your rom (cm12) bumb enabled ? (edit : "Currently, all official CyanogenMod ROMs use loki tool to install the kernel on the LG G Pad 8.3 v500" )
The current official nightly still uses loki so it still requires the 4.2.2 aboot. There is another thread about switching boot loaders which will also downgrade aboot with flashable zip. If the rom you are installing is pre bumped, then an aboot from 4.4.2 will work, but i still recommend downgrading aboot to 4.2.2 version for better compatibility with older roms and official cm.
so i installed the recovery, after i push the power button in the factory reset menu to load the recovery, the lg logo screen is very dark just like when youre in download mode, is this normal? i'm on kitkat bootloader
auleu said:
so i installed the recovery, after i push the power button in the factory reset menu to load the recovery, the lg logo screen is very dark just like when youre in download mode, is this normal? i'm on kitkat bootloader
Click to expand...
Click to collapse
Yes, that is normal.
Deltadroid said:
Yes, that is normal.
Click to expand...
Click to collapse
and if i install a rom and at the end says something like not loki exploitable does this mean that the rom is not bumped?
auleu said:
and if i install a rom and at the end says something like not loki exploitable does this mean that the rom is not bumped?
Click to expand...
Click to collapse
Yes
Deltadroid said:
Yes
Click to expand...
Click to collapse
if i enable loki support in cwm can i install a non bumped rom ? or what does that setting do?
auleu said:
if i enable loki support in cwm can i install a non bumped rom ? or what does that setting do?
Click to expand...
Click to collapse
Enabling loki support in cwm is deprecated and wont do anything. The problem is that you need to downgrade your aboot so that the Rom you are installing can execute it's scripts properly. There is a thread here that provides flashable zip files to switch bootloaders. You will want to choose the bootloader package with the downgraded aboot if you want to install older ROMs that have not been updated to use bump yet.
http://forum.xda-developers.com/showthread.php?p=52910560
does cwm have a rom size limit? im trying to sideload the stock lollipop rom with over 1gb size and gives error. failed to write data 'protocol fault (no status)'
auleu said:
does cwm have a rom size limit? im trying to sideload the stock lollipop rom with over 1gb size and gives error. failed to write data 'protocol fault (no status)'
Click to expand...
Click to collapse
This recovery is probably better suited for lollipop
http://forum.xda-developers.com/showthread.php?p=61363260
Deltadroid said:
This recovery is probably better suited for lollipop
http://forum.xda-developers.com/showthread.php?p=61363260
Click to expand...
Click to collapse
i've installed that one, it worked but didnt tried sideloading it, instead i copied it to sdcard. also its strange that cwm dosent have mount sdcard option
Android One Universal STOCK ROMs [MM/LP]
These ROMs were dumped using the command "dd", 100% Stock without any modification.. These roms were put together for users who wants to fall back to google stock rom, And also for users who are having issues while installing the latest OTA. Nothing is removed from the original rom, and all signatures are intact. And Lastly, please take the time to read the instructions, FAQ, carefully and thoroughly before proceeding....
List of devices with known compatability
Code:
[CENTER][SIZE="4"]Cherry Mobile One G1 (Philippines)
General Mobile 4G (Turkey)
I-Mobile IQ II (Thailand)[/SIZE][/CENTER]
DOWNLOAD
[ AFH | DRIVE ]
FLASHING PROCEDURE :
Download the ROM
Move the file to internal storage
Reboot to TWRP custom recovery
Backup your current ROM (just in case)
Locate the file and install
Reboot and have patience while it boots up... It will take about 15-20 minutes
In case you want to fall back to stock recovery, ensure that "MOUNT SYSTEM PARTITION READ-ONLY" is enabled from the twrp MOUNT section prior to installation, otherwise uncheck it
Click to expand...
Click to collapse
FASTBOOT METHOD
Extract all the images to adb folder and ensure that USB Debugging is enabled.
Code:
#! adb reboot bootloader
#! fastboot flash system system.img
#! fastboot flash boot boot.img
#! fastboot flash modem radio-modem.img (For Marshmallow MRA58Y Rom only)
#! fastboot reboot
Frequently Asked Questions :
1. Is it compatible with my device?
Yes, as long as you are using an Android One 2nd generation [seed] with a qcom 410 processor (msm8916).
2. Will I still be able to recieve the official OTA updates in the near future?
Yes, as long as you've never rooted, changed recovery, or any other modification on your system.
In case you have rooted your device, all you have to do is reflash the ROM when a new ota arrives and you'll be fine
3. Do I need to Wipe my Data and cache partitions before attempting to install the ROM?
No, but it is recommended especially if you are having too many apps FCs
If you are having apps FCs, try clearing the app data of the affected app, or try hard reset.
If all else fail, do a clean install.
4. Got stuck with "Patching system image unconditionally"?
It might be a bad download
Always verify the hash prior to proceeding (check the howto verify the MD5sum below)
Wipe the system partition just in case
MD5 Signature
How to Verify the MD5 signature?
If you are running Windows just download HashTabs and install. Right click on the downloaded file then click properties and look for "FILE HASHES" tab, verify if md5 hash are the same. On unix based system just execute this line in the terminal "md5sum SPROUT4-STOCK-ROM-LMY47V.zip". On your phone, just use ES explorer and then click properties then tap "Show Checksum" then compare the md5 hash. If the file hashes are identical you are good to go, Otherwise, redownload the file again due to bad probably.
[MRA58Y] efa811732dd54ccdbe73a4cb8bdb085c
[LUZ56M] 5a58c232a6e5667c123236175a070a7e
Flash at your own risk :good:
MISC
Code:
[CENTER][URL="https://goo.gl/j7F8Mz"]DRIVE[/URL][/CENTER]
reserved 2
reserved 3
Thanks a lot for this. I will test it now and will let you know.
kiksilog said:
Thanks a lot for this. I will test it now and will let you know.
Click to expand...
Click to collapse
:good: :highfive:
General Mobile 4G Dual
1cefire said:
:good: :highfive:
Click to expand...
Click to collapse
General Mobile 4G Dual support?
My G1 is now running Marshmallow. It did took awhile on the boot screen but other than that :good:
Thanks again!
kiksilog said:
My G1 is now running Marshmallow. It did took awhile on the boot screen but other than that :good:
Thanks again!
Click to expand...
Click to collapse
Rom files is'nt enough folders, not even as work general mobile 4g , I have already My work is turkish forums . he doesn't come back lolipop
Anyone has the stock rom for lava pixel v1 (2nd gen android one)??india
JaxaPRO said:
General Mobile 4G Dual support?
Click to expand...
Click to collapse
Yes
kaankulahli said:
Rom files is'nt enough folders, not even as work general mobile 4g , I have already My work is turkish forums . he doesn't come back lolipop
Click to expand...
Click to collapse
Although we had different Lollipop rom build no., our device and roms are basically the same. Since Android M arrived we all share the same build numbers. How did I know this? By verifying the MRA58Y ota and comparing all the hashes including the radio-modem.img I found out we all share the same Android M stock rom. And lastly, the MRA58M ota will not touch any other partition other than the system, boot and modem, so basically, all you need is the system.img, boot.img and radio.modem.img to be able to update to Android M. The rest of the partitions are useless when it comes to updates
sourav4ganguly said:
Anyone has the stock rom for lava pixel v1 (2nd gen android one)??india
Click to expand...
Click to collapse
Sorry dude, I cant provide you the stock rom for Lava Pixel v1 since I dont own the device.
@1cefire
Can your TWRP files found here
androidfilehost dot com/?w=files&flid=43419
be used to root Marshmallow?
if yes, which one to use? (i.e. blue, classic, darkplay)
thanks.
@kiksilog
Any recovery will do as long as it runs on this device. Unfortunately, Marshmallow requires a permissive kernel, so far no one has manage to build an insecure kernel for seed without any issue. Even the latest beta supersu with a modded sepolicy boot.img failed to boot. Android M for seed is unrootable for now, hopefully supersu will get an update to support our latest OS
Oi
Android Marshmallow 6.0.1!!!
In case someone might consider upgrading to Android M 6.0.1 MMB29K
- install it via custom recovery philz / twrp / fastboot (visit the first page for more info)
- the rom contains system.img and boot.img only (the only partitions required to upgrade)
- the rest of the partitions were removed and will be provided separately for each device
Huge thanks to @dabotsonline for the link
How about posting the download url of the OTA update 6.0.1 file which I understand is only less than 90 mb? Thanks.. :fingers-crossed:
1cefire said:
Android Marshmallow 6.0.1!!!
In case someone might consider upgrading to Android M 6.0.1 MMB29K
- install it via custom recovery philz / twrp / fastboot (visit the first page for more info)
- the rom contains system.img and boot.img only (the only partitions required to upgrade)
- the rest of the partitions were removed and will be provided separately for each device
Huge thanks to @dabotsonline for the link
Click to expand...
Click to collapse
Wow, very helpful (Y)
1cefire said:
Android Marshmallow 6.0.1!!!
In case someone might consider upgrading to Android M 6.0.1 MMB29K
- install it via custom recovery philz / twrp / fastboot (visit the first page for more info)
- the rom contains system.img and boot.img only (the only partitions required to upgrade)
- the rest of the partitions were removed and will be provided separately for each device
Huge thanks to @dabotsonline for the link
Click to expand...
Click to collapse
are you a time traveler?
Yeah everybody. We already made it before google ????.
Wileyfox Swift cihazımdan Tapatalk kullanılarak gönderildi
@1cefire can i install it in aq4501???
Installation
1. Place TWRP-3.0.0-0.zip file in Sd card
2. Reboot in Recovery Mode
3. Install the Recovery zip
4. Reboot Recovery
:fingers-crossed::victory:
Downloads
TWRP 3.0.0-0
Huge Thanks to
TeamWin for the source, Varun.Chitre15 Sprout Device Tree,
Swapnil Solanki To Port It for Sprout
DeepSahota said:
Installation
1. Place TWRP-3.0.0-0.zip file in Sd card
2. Reboot in Recovery Mode
3. Install the Recovery zip
4. Reboot Recovery
:fingers-crossed::victory:
Downloads
TWRP 3.0.0-0
Huge Thanks to
TeamWin for the source, Varun.Chitre15 Sprout Device Tree,
Swapnil Solanki To Port It for Sprout
Click to expand...
Click to collapse
Okay Thanks
You're Welcome
DeepSahota said:
You're Welcome
Click to expand...
Click to collapse
Can I flash using stock recovery?
Nope, you can flash it with TWRP/CWM/PHILLZ and your bootloader needs to be unlocked.
Will it work on 1st generation android one device ?
DarkHeart Z said:
Will it work on 1st generation android one device ?
Click to expand...
Click to collapse
Yes it works perfectly
DeepSahota said:
Installation
1. Place TWRP-3.0.0-0.zip file in Sd card
2. Reboot in Recovery Mode
3. Install the Recovery zip
4. Reboot Recovery
:fingers-crossed::victory:
Downloads
TWRP 3.0.0-0
Huge Thanks to
TeamWin for the source, Varun.Chitre15 Sprout Device Tree,
Swapnil Solanki To Port It for Sprout
Click to expand...
Click to collapse
Hii ....
Is it possible to flash this zip via fastboot with bootloader unlocked????
If yes, plz let me know how to flash.
Bcoz I'm using canvas a1 4gb. I want to backup my stock Android . I unlocked bootloader and I'm failing in flashing custom recovery. I used Android one tool kit and Aone pro v2 tool kits. Nothing worked. I also tried to flash custom recovery via sp tool. Still I'm on stock recovery now.
muthur774 said:
Hii ....
Is it possible to flash this zip via fastboot with bootloader unlocked????
If yes, plz let me know how to flash.
Bcoz I'm using canvas a1 4gb. I want to backup my stock Android . I unlocked bootloader and I'm failing in flashing custom recovery. I used Android one tool kit and Aone pro v2 tool kits. Nothing worked. I also tried to flash custom recovery via sp tool. Still I'm on stock recovery now.
Click to expand...
Click to collapse
Here's the driver and Toolkit download and install custom recovery
Follow my instructions
1, Install ADB drivers.
2, Then Extract Toolkit zip and run Toolkit CMD file.
3, Choose Your Task you want
Enjoy
https://drive.google.com/file/d/0B5wsXNzlO7M1SG1FZUltT3hHYjA/view?usp=docslist_api
https://drive.google.com/file/d/0B5wsXNzlO7M1SG1FZUltT3hHYjA/view?usp=docslist_api
Will it work on in focus m530
This is only for the Android One devices.
Will it work on "ASUS ZenFone 5"?
Model: ASUS_T00J
Product: WW_A501CG
Android: 5.0 lollipop
API: 21
CPU: 1.60 GHz (4 core)
GPU: PowerVR SGX 544 MP2
RAM: 2 GB
sn: EBAZCY00T254
PD: 29-dec-2014
Will it work on my intex aqua raze
Will it work on intex aqua raze my phone has MT6735m chipset
where can i find the last twrp as twrp flashable zip file ?
TWRP-3.0.0-0.zip failed for signature reasons
DeepSahota said:
Yes it works perfectly
Click to expand...
Click to collapse
Original samsung recovery rom refuses to flash file TWRP-3.0.0-0.zip and reports signature failure.
Dude, can you help me?
If you can, can you tell me how do i unlock my bootloader?
My phone is an ASUS Zenfone GO Live/dtv (ZB551KL- ASUS XD013)
thanks, Caíque...
My english it's not so good because i'm Brazzilian and i've got 13 years old
please, help me ;-;.
MihaiSG said:
Nope, you can flash it with TWRP/CWM/PHILLZ and your bootloader needs to be unlocked.
Click to expand...
Click to collapse
How to unlock bootloader for: SM-T837P?
I couldn't find anything for this device to do this...
Thnx in advance!
Wher
I'm trying to install the CM11 ROM (Cyanogenmod) in my SONY XPERIA SP 5303, already unlocked the bootloader and my ROM version is Android 4.3 12.1.A.1.201 (kernel version 3.4.0-perf-ga1d7493) that are DoomLord requirements, however when trying to install the kernel starting the fastboot mode I get the following error:
How could not put the right image in the post, I'm leaving the link just below. Put spaces in (http) is only copy and remove the spaces.
Thank you!!!
h t t p://imagizer.imageshack.us/a/img922/5859/Lz5loO.jpg
To install any CM ROM, just flash twrp recovery instead.
You can find install instructions and download links in this thread:
http://forum.xda-developers.com/showthread.php?t=3309938
Sent from my Xperia SP using Tapatalk
I managed to resolve the error, install the kernel and cm11 . If someone is with this problem I simply installed a more current version of FlashTool and also the minimal adb and fastboot , although I used the FlashTool . Aparentimente the error was caused by lack of a device driver.