Related
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
hiandro said:
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
Click to expand...
Click to collapse
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
skeevy420 said:
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
Click to expand...
Click to collapse
can u give me link to download latest CWM please.
hiandro said:
can u give me link to download latest CWM please.
Click to expand...
Click to collapse
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
skeevy420 said:
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
Click to expand...
Click to collapse
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
hiandro said:
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
Click to expand...
Click to collapse
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
skeevy420 said:
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
Click to expand...
Click to collapse
Yeah, i tried to restore backup using cm10 recovery and although it said cant restore .android.secure something like that(iam not quite sure) it restored system as well as data.
The thing is i like mokee os .its speed, clean and clear... ecetra but it is not jelly bean.can't we have a cm10 tweaked and modified for bravo.of course I love your PA jelly bean there are lots of tablet tweaks can you also add some other functions like in pimp my rom.
And thanks man for answering my queries
Long story short a custom kernel completely screwed up the graphics on my N4 CM11 so I'm trying to flash the original kernel from the ROM which is NOWHERE to be found in the cyanogen site.
Anyone got a link?
MGREX said:
Long story short a custom kernel completely screwed up the graphics on my N4 CM11 so I'm trying to flash the original kernel from the ROM which is NOWHERE to be found in the cyanogen site.
Anyone got a link?
Click to expand...
Click to collapse
Just reflash the rom.
If you don't want to, tell me what version of cm11 your'e running and i'll make a flashable kernel zip :good:
or pull the boot.img out of the rom zip and use the flashify app to flash it. the boot.img is the kernel. but honestly, it sounds like you have absolutely no idea what you are doing. if you have any questions, please ask, im willing to help. can you explain what happened?
Yeah I screwed up, didn't notice it wasn't CAF
22sl22 said:
If you don't want to, tell me what version of cm11 your'e running and i'll make a flashable kernel zip :good:
Click to expand...
Click to collapse
It's 11.0-InstallerXNPQ08Q
Thanks!
So after a reboot to enter recovery my N4 is stuck in the splash screen with the white google logo.
This is getting worse by the minute...
MGREX said:
So after a reboot to enter recovery my N4 is stuck in the splash screen with the white google logo.
This is getting worse by the minute...
Click to expand...
Click to collapse
just fastboot flash a recovery, this shouldnt an issue. did you flash a recovery before, or just boot one? it makes a difference if it sticks around or not.
simms22 said:
just fastboot flash a recovery, this shouldnt an issue. did you flash a recovery before, or just boot one? it makes a difference if it sticks around or not.
Click to expand...
Click to collapse
I'm able to force-access recovery and CWM but that's it, once it boots it gets stuck on the splash screen, and thanks to the lack of a SD port I'm unable to easily load a kernel or ROM, and despite having the android SDK I'm unable to sideload the file through adb on Windows.
Any ideas? besides trying the adb through Linux (I'm doing that now)
Here's the flashable kernel zip taken from Snapshot M7 build :good:
Okay now it gets stuck in the cyanogenmod boot animation
Any ideas? that don't involve wiping everything I mean
simms22 said:
or pull the boot.img out of the rom zip and use the flashify app to flash it
Click to expand...
Click to collapse
Can't do since it no longer boots into android, but I tried to do what you say and sideload the zip but I get a "installation aborted" error on CWM
MGREX said:
Can't do since it no longer boots into android, but I tried to do what you say and sideload the zip but I get a "installation aborted" error on CWM
Click to expand...
Click to collapse
What about TWRP?
Sent from my Nexus 4 using Tapatalk
22sl22 said:
What about TWRP?
Click to expand...
Click to collapse
You mean installing TWRP?
BTW that problem is with the kernel I assembled using a CM11 ROM, your zip actually does boot into cyanogenmod but it gets stuck in the CM boot animation
Okay I'm not sure why or how, but this time it booted alright:laugh::highfive::good:
Thank you guys for the assistance, I'll do a full backup in case it decides to crash again so I can do a total wipe and flash a new ROM from scratch
MGREX said:
Okay I'm not sure why or how, but this time it booted alright:laugh::highfive::good:
Thank you guys for the assistance, I'll do a full backup in case it decides to crash again so I can do a total wipe and flash a new ROM from scratch
Click to expand...
Click to collapse
No problem
Do a titanium backup that backs up all your apps with data. Always have a backup so if things do go wrong you can just wipe and restore apps afterwards :good:
Sent from my Nexus 4 using Tapatalk
@o-l-a-v have made latest twrp 2.8.6.0 recovery with f2fs for flashing on fota partition. I publish it here bcs there is no development behind it. It works with latest cm12 nightlies
f2fs is untested report pls
All thanks to @o-l-a-v
Install through fastboot:
fastboot flash recovery
https://mega.co.nz/#!3gRwGZiK!sXMsMx1GGwUVkTCCsr8ntZekCE-o-hB4DDp6wlhVQqA
New version again
You don't need any app for flashing, use fastboot, see above
be careful if you write: fastboot flash boot you won't be able to boot
Cool, what ROMs did you test this on ?
OmarEinea said:
Cool, what ROMs did you test this on ?
Click to expand...
Click to collapse
i´m on liquid, but it works on every no stock rom,i used previous version on all your roms
i have made it bcs @championswimmer has not amami support for twrp in his recovery manager only for philz and i prefer twrp
funiewski said:
I have made latest twrp 2.8.0.1 recovery for flashing on fota partition. I publish it here bcs there is no development behind it.
Install through fastboot:
fastboot flash recovery fotaZ1cTWRP2.8.0.1.img
https://dl.dropboxusercontent.com/u/17658154/fotaZ1cTWRP2.8.0.1.img
Click to expand...
Click to collapse
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?
Rekoil said:
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?
Click to expand...
Click to collapse
That was TWRP developer @Dees_Troy who found the possibility of using fota partition on xperia devices for recovery flashing. Here: http://forum.xda-developers.com/showpost.php?p=38640389&postcount=2
You access it in usual way, Sony logo+led light press volume+. Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed. If you are flashoholic like me it is quite a pain. With recovery on fota partition it is no longer a problem. @championswimmer has made a small paid app for flashing recovery on fota, but as i wrote before it does not support twrp for amami only philz and you can flash it easily with fastboot. This works only on aosp and cm roms, if you want to overwrite recovery on fota you can either use flashtool and flash only fota, uncheck all other boxes or you can use recovery manager i mentioned earlier.
funiewski said:
Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed.
Click to expand...
Click to collapse
Nice, expirienced same problems.
Thanx @funiewski
Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?
CoolDevelopment said:
Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?
Click to expand...
Click to collapse
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon
funiewski said:
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon
Click to expand...
Click to collapse
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.
How does it work that the phone enters recovery from FOTA partition and not kernels internal recovery?
Rekoil said:
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.
Click to expand...
Click to collapse
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me
funiewski said:
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me
Click to expand...
Click to collapse
Yeah but it is still executing the kernel from the boot partition, so if you **** up boot partition you'll **** up recovery, so it's not much of a recovery. It just loads data from the FOTA partition. A true recovery has its own kernel.
On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?
paulle said:
On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?
Click to expand...
Click to collapse
Exactly in same way as this one.
@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well
russel5 said:
@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well
Click to expand...
Click to collapse
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here
funiewski said:
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here
Click to expand...
Click to collapse
Not stock, but for stock ROM with stock ramdisk (except RIC is disable)
This boot NOT have any recovery, only work with FOTA recovery
View attachment boot.zip
Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)
o-l-a-v said:
Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)
Click to expand...
Click to collapse
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp
funiewski said:
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp
Click to expand...
Click to collapse
Yes, stock CM kernel. Hm. I'll try again. Eventually try that custom kernel.
Hi my phone seems to hate custom roms like cyamogenmod and gapps because everytime i flash them a bootloop inevitably comes to haunt me. Other roms like Albe95 Ports work. http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564
My current rom is Phoenix Rom. http://forum.xda-developers.com/showthread.php?t=2349584
The roms listed above work flawlessly.
A rom that I wanted to try was cyamogenmod 12.1 optimized by JDC team but it wouldnt boot. I followed exact instructions for each rom. Every time i used TWRP.
Could my problem be that gapps screw with the custom rom ?
Google apps are integrated in phoenix rom and albe95.
Maybe thats why they work ?
Please help.
Thank you for youre time.
JaguarBeast said:
Hi my phone seems to hate custom roms like cyamogenmod and gapps because everytime i flash them a bootloop inevitably comes to haunt me. Other roms like Albe95 Ports work. http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-lollirom-official-1-0-t3049564
My current rom is Phoenix Rom. http://forum.xda-developers.com/showthread.php?t=2349584
The roms listed above work flawlessly.
A rom that I wanted to try was cyamogenmod 12.1 optimized by JDC team but it wouldnt boot. I followed exact instructions for each rom. Every time i used TWRP.
Could my problem be that gapps screw with the custom rom ?
Google apps are integrated in phoenix rom and albe95.
Maybe thats why they work ?
Please help.
Thank you for youre time.
Click to expand...
Click to collapse
You can easily test that theory by not flashing Gapps. Just only flash the rom and try to boot it.
Also are you running a Lollipop bootloader and modem?
Ive tried flashing only custom rom but the bootloop comes back. Right now i am running a lollipop modem and bootloader.
JaguarBeast said:
Ive tried flashing only custom rom but the bootloop comes back. Right now i am running a lollipop modem and bootloader.
Click to expand...
Click to collapse
Ok do this:
Backup everything that you want to save stored on your internal storage.
1. Make sure you are running the latest TWRP. This is important because using an outdated version will not let you boot the rom.
2. Start TWRP and do a advanced wipe. Format /data (this will wipe your internal storage), format /system, format /cache and /dalvik.
3. Flash the rom.
Unfortunately that does not help. I have advanced wiped ever time before flashing rom. Maybe permisions are the problem ?
JaguarBeast said:
Unfortunately that does not help. I have advanced wiped ever time before flashing rom. Maybe permisions are the problem ?
Click to expand...
Click to collapse
What version of TWRP are you using? And did you try booting it without simcard and sd card?
Im using 2.8.7.2 twrp. I havnt tried to boot without sd or sim. Would that be the problem ?
JaguarBeast said:
Im using 2.8.7.2 twrp. I havnt tried to boot without sd or sim. Would that be the problem ?
Click to expand...
Click to collapse
No idea. I'm just guessing because that rom should just boot.
Are you sure the file you downloaded is not damaged? Check the MD5 signature. For example, the latest version of the JDC CM rom has MD5:
3a1af890b87c11256c943759459ec3e4
So transfer the file to your phone. Then download a MD5 checker from the market and compare it.
Md5 matches. Looks like the insides of my phone are screwed up
Reparation your device
As those are caused by a screwed partition
As a reparation fixes this
You are going to need :-
0.a PC
1.a PIT file for your Galaxy s4 (depending on your variant)
2.Odin
3.Samsung USB drivers installed in the PC
Sent from my GT-I9505 using Tapatalk
Start with flashing the stock rom using odin. Then go for root,then recovery and then try flashing. I had the same problem but it never bothered me after flaahing the stock.
Hi,
I am currently using Miui 7 (V 6.4.28).
I wanted to try ED300 CM 12.1. So I did a full backup of the ROM>format all>Flashed the new ROM. But I see that the Miui boot image/splash image still present there, even if I completely erased all the partition.
Question is, how I can flash the boot image of Lenovo a6000/plus? Additionally, can someone also provide the new Lenovo stock boot logo. I somewhat like that more.
Thanks.
Meetwidargha said:
Hi,
I am currently using Miui 7 (V 6.4.28).
I wanted to try ED300 CM 12.1. So I did a full backup of the ROM>format all>Flashed the new ROM. But I see that the Miui boot image/splash image still present there, even if I completely erased all the partition.
Question is, how I can flash the boot image of Lenovo a6000/plus? Additionally, can someone also provide the new Lenovo stock boot logo. I somewhat like that more.
Thanks.
Click to expand...
Click to collapse
Thats due to the twrp 3.0.0 which was included with MIUI 7. Just flash this old twrp 2.8.6.1 version by sevenmax.
sasukay said:
Thats due to the twrp 3.0.0 which was included with MIUI 7. Just flash this old twrp 2.8.6.1 version by sevenmax.
Click to expand...
Click to collapse
I try to flash twrp 2.8.6.1 by sevenmax but boot splash is not changed it still mi boot splash [emoji20]
Sent from my HM2014817 using XDA-Developers mobile app
well you can flash the stock rom
backgamons said:
I try to flash twrp 2.8.6.1 by sevenmax but boot splash is not changed it still mi boot splash [emoji20]
Sent from my HM2014817 using XDA-Developers mobile app
Click to expand...
Click to collapse
Well, I did a bit of digging but couldn't find the splash image ditectory in the MIUI boot and recovery image. But, Im pretty sure that when I changed the recovery, the splash image also turned back to stock lenovo logo.
Meetwidargha said:
Hi,
I am currently using Miui 7 (V 6.4.28).
I wanted to try ED300 CM 12.1. So I did a full backup of the ROM>format all>Flashed the new ROM. But I see that the Miui boot image/splash image still present there, even if I completely erased all the partition.
Question is, how I can flash the boot image of Lenovo a6000/plus? Additionally, can someone also provide the new Lenovo stock boot logo. I somewhat like that more.
Thanks.
Click to expand...
Click to collapse
Just flash any stock rom, then do a full wipe(dalvik, cache, system, data), then flash ED300's cm 12.1 rom.. U will get the stock splash image.
Hit thanks, if i helped!!
Flash it with TWRP
mshoaib7 said:
Flash it with TWRP
Click to expand...
Click to collapse
T
his worked for me. I read a bit about where the splash image is stored, but couldn't find the right location, since it depends on boot partitions and is not just any jpg file stored at some particular location. But, all thanks to you, I got to know how to replace it.
I'm having exams right now, but I'll surely be making some custom splash images for our phone. Thanks a lot.
And, one more thing, do we need to add all those manifest, otcert, releasekey and stuff in the META-INF folder or just update-binary and updater-script will do.? :silly:
sasukay said:
T
his worked for me. I read a bit about where the splash image is stored, but couldn't find the right location, since it depends on boot partitions and is not just any jpg file stored at some particular location. But, all thanks to you, I got to know how to replace it.
I'm having exams right now, but I'll surely be making some custom splash images for our phone. Thanks a lot.
And, one more thing, do we need to add all those manifest, otcert, releasekey and stuff in the META-INF folder or just update-binary and updater-script will do.? :silly:
Click to expand...
Click to collapse
No, you don't need those files. Update-binary and updater-script is all you need in meta-inf folder. I was just too lazy to remove those files ?
I have the same problem . When I start my phone the MI logo appears followed by the Cyanogen Mod boot animation . How do remove it? I have installed another recovery but still same prob!
Pls built many kinds of splash boot logo.
mshoaib7 said:
Flash it with TWRP
Click to expand...
Click to collapse
thanks its work for me
mshoaib7 said:
Flash it with TWRP
Click to expand...
Click to collapse
How to make custom splash screen for lenovo a6000 /plus
Hi I am experiancing same problem .my phone a 6000 plus ,didn't show Lenovo logo on startup. .also not load to antroid ... previously it was lolipop I tried to flash to a another rom by using Mi flash ...do you have any solution for this ...I want to use this phone no need of any particular rom ..just want to use this phone ((very sad))