[ for dev only ][ClockworkMod]Touche Recovery v6.0.2.7[ based [ xd.bx ] recovery - Galaxy S III Mini Android Development

WARNING FOR DEV ONLY AT THIS STAGE ​
hey all here recovery based from xd.bx but with touche screen Option and more features is just fresh and wana share it with all Galaxy S III Mini user just flash as PDA with odin but have boot only to recovery i try to flash back and report here if any one can try and feedback are good
WE have more feature
1- you can no only backup but also creat flashable.zip image and share rom with every one
2- have many option not tested just feed if have problem for all other feature just flash and see by ur self is beter than explain here

Credit
xd.bx for working CWM and config files
Me :silly:
Flyhalf205 soon make this recovery working
blackknightavalon for test
OliverG96 for tip's and also sharing his work

Now if any dev have know about why the phone boot only to recovey when i choos reboot system i have samsung gt xxxx galaxy s III mini and after recovery no boot to system why ? :good:
Dont forget is colaborate work all user here have credit

Hi,
Make sure you have both j4fs and param loaded. Mount /mnt/.lfs before loading param. Also you must patch kernel (patch is in the other thread)

For sure you're building this from the cwn builder yeah?
Wich recovery are you using as base?
Enviado desde mi GT-I8190 usando Tapatalk 2

OliverG96 said:
For sure you're building this from the cwn builder yeah?
Wich recovery are you using as base?
Enviado desde mi GT-I8190 usando Tapatalk 2
Click to expand...
Click to collapse
Hi used xd.bx recovery and also grafic.c and fstab i any one can try show me dmesg (grep -i param grep -i j4fs)
this solve that issue via modifying param and j4fs drivers

Any one can flash this recovery and give me
dmesg (grep -i param grep -i j4fs) log in .txt and PM me this is for resolving the problem thank you

Flashed this via Odin. Every time I try to reboot it just reboots straight into recovery. Good first attempt, though.

blackknightavalon said:
Flashed this via Odin. Every time I try to reboot it just reboots straight into recovery. Good first attempt, though.
Click to expand...
Click to collapse
yes need fix into j4fs driver i need dmesg (grep -i param grep -i j4fs) if any one can give me this in txt format is great

Testing New Build tonight if is OK and booted normaly I post it Here ^^ waiting ... backing up .... if booted change thread from for dev to fix

some result boot only to recovery

spawk said:
some result boot only to recovery
Click to expand...
Click to collapse
Hi,
Make sure you use the kernel from my recovery and that your recovery.rc mounts /mnt/.lfs before inserting param.ko. Afaik these are the only two requirements to fix the "reboot into recovery loop" problem.

in half of February I go back to my 2nd pc it works better that the dinausaure I have between hand actuely I look has its place once the meantime if one wants to devote himself to advance the project is the welcome actualy I run pc with some hardawre lost ( no keyboard , and have big problem with java and flash
PS: why in half of february because my 2nd pc are in another country ( africa )

First of all congrats in the devs for this achievement.
I'm getting pms about people that are flashing this custom recoverys and messing their devices pretty good ,some of them thinking that this is just root!
Once you install this recoverys the device will not be be same, you will loose your warranty etc, it will always show System status As Custom!
So far there is no clear way of reverting to original status.
Also after installing custom recoverys some users end up with a soft-brick after going back to official and is not easy to the average user to bring it back to life.
Make sure you post a proper description of this files and what they will to to users devices,allot of users do not understand what this is and just flash it anyway!
Also for those devs that are working in custom recoverys ,Try to find a way of reverting the device to a proper working state and post such info,after all you know more about it that me.
People are assuming that this is like older devices that you could just flash the custom kernel to acquire root,well this aint just a custom kernel.
Regards
faria

I have briked phone by instaling rom and not this recovery this recovery don't brick any device you have bootlop to recovery now user talk about brick by installing recovery is another one just see in thread dev section and find is non complet recovery now in this thread need only i decompile recovery.img and aplying patche into boot.sh now the recovery see only 1 boot ( into recovey ) when patch are done get reovery like CWM but diferance are in touche I have used corect files now in first post we have WARRNING IN RED and also in BIG letter and the warning talk about this recovery at this stage is only for devlopper user know how to etc etc

spawk said:
I have briked phone by instaling rom and not this recovery this recovery don't brick any device you have bootlop to recovery now user talk about brick by installing recovery is another one just see in thread dev section and find is non complet recovery now in this thread need only i decompile recovery.img and aplying patche into boot.sh now the recovery see only 1 boot ( into recovey ) when patch are done get reovery like CWM but diferance are in touche I have used corect files now in first post we have WARRNING IN RED and also in BIG letter and the warning talk about this recovery at this stage is only for devlopper user know how to etc etc
Click to expand...
Click to collapse
Did you post how to backup the original recovery ? No
You really expect users to know how to recompile the recovery image!? Did you post such info? No
My statement stands.
I never said that recovery's bricked the devices,I said that it modefys the device in a manner that is causing problems.

faria said:
Did you post how to backup the original recovery ? No
You reallyexpect users to know how to recompile the recovery image!? Did you post such info? No
My statement stands.
I never said that recovery's bricked the devices,I said that it modefys the device in a manner that is causing problems.
Click to expand...
Click to collapse
I have posted original recovery yes is in dev thread and is flashable by odin here is http://forum.xda-developers.com/showthread.php?t=2093727
and I have open thread for make ONE thread with all referance to rom CWM and Tweak this is more clear when user come in forum he see first sticked thread wirh all link to tool rom custom rom but i can't make it for my bad english this need good writer

OK now I have 4 week to learen how to fix this now if any one have link explain from A to Z how to mod make compile decompile .... relative to Recovery just PM

Related

[Q] Recovery for Maxx 3g AX51 - any one port recovery for this device.

Plz any one port custom recovery for Maxx 3g AX51,
partition ext4, MT6572 processor ,resolution 480x854, Android 4.2.2, plz any developer response my problem.
If recovery not port then , plz give me backup rom procedure ,and flash procedure.
when i take backup with onandroid or mtk tool, its create system.ext4.tar which is unflashable, i want in .img format.
Also It has fastboot not able to flash any other device recovery gives error,
--> partition 'recovery' not support flash <-- why plz reply any developer.
This is not a fast food restaurant. You don't order something and it'll be delivered.
This is a development site, where people learn from each other and do research to eventually make what they want themselves.
In your case I would start by finding the closest matching device that does have a recovery. And and then ask the developer there how to proceed in making a recovery for your own device.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
SMillerNL said:
This is not a fast food restaurant. You don't order something and it'll be delivered.
This is a development site, where people learn from each other and do research to eventually make what they want themselves.
In your case I would start by finding the closest matching device that does have a recovery. And and then ask the developer there how to proceed in making a recovery for your own device.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
Click to expand...
Click to collapse
ya i know ...
i also had mentioned
flashing of recovery through fast boot mode.
fastboot flash recovery /sdcard/recovery. img
gives this error.
partition 'recovery' not support flash
why not flash recovery.img ,why gives error plz reply my query
mansuri.shoaib39 said:
ya i know ...
i also had mentioned
flashing of recovery through fast boot mode.
fastboot flash recovery /sdcard/recovery. img
gives this error.
partition 'recovery' not support flash
why not flash recovery.img ,why gives error plz reply my query
Click to expand...
Click to collapse
Because I did not tell you to flash the recovery of another device, I told you to seek help from the creator.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
SMillerNL said:
Because I did not tell you to flash the recovery of another device, I told you to seek help from the creator.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
Click to expand...
Click to collapse
its my stock backup recovery. img
found same configuration mobile cwm recovery
hello i had found Gionee P2 custom recovery which is same configuration as Maxx 3G AX51, after flashing Gionee P2 recovery to Maxx 3G AX51, it does not goes to recovery mode just restart 2 times and normal boot to start mobile.
so what to do... plz help some one...
Gionee P2 custom recovery link is here below.
https://www.dropbox.com/s/570k7dtf90y3lfo/gionee_P2cwm_recovery.img
Recovery ported my self for Maxx AX51
hello everyone i had ported touch recovery for this mobile Maxx 3G AX51 .... i will upload soon ...
No bug everything is working fine. ... great recovery...
no post .,.... or requests for recovery.... i think no more user available for this mobile.... after user request ... i will upload..... because no use of this recovery in this forum....

[Q] Stuck on Sony Logo

So I thought of installing a new ROM to my XZU today. First I rooted my device using the following guide : https://www.youtube.com/watch?v=BkQT3nX5yWM. (As I had updated my device to Android 4.4.4 and had .108 FW). I successfully rooted the phone and took a TA Backup. Afterwards, I went on to unlock the bootloader and unlocked it successfully as well. As I wanted to install the ParanoidAndroid 4+ ROM, I downloaded it and got the boot.img from the ZIP file, and flashed it using the Flashtool. However, afterwards, when I tried to go the recovery mode, it is stuck on the Sony Logo, and doesn't blink the notification LED in order to do so.
Did I do anything wrong? I am quite a noob when it comes to XZU related stuff..so I would really appreciate if someone can help me out..
Thanks in advance!
EDIT: (Thought of editing this thread rather than deleting it so that it could be an help for someone who faces a similar problem) I was able to make my device up and running again by flashing the FTF found in this thread: http://forum.xda-developers.com/showthread.php?t=2798690.
Now, I have again come to the status where I have installed a recovery successfully and unlocked my bootloader, and I want to install PA 4+ to my device. Would really appreciate if anyone can guide me on how to do this
It doesn't sound like you did any thing wrong.
Do you have [NUT]'s recovery installed now?
Do a nandroid backup if you do, saves the whole flashing a FTF step if something goes wrong
Did you get the correct PA? what date?
PA should install fron [NUT]'s recovery or you could hotboot the boot.img with flashtool (this wont over write you current kernel) this will let you test if it does work
blueether said:
It doesn't sound like you did any thing wrong.
Do you have [NUT]'s recovery installed now?
Do a nandroid backup if you do, saves the whole flashing a FTF step if something goes wrong
Did you get the correct PA? what date?
PA should install fron [NUT]'s recovery or you could hotboot the boot.img with flashtool (this wont over write you current kernel) this will let you test if it does work
Click to expand...
Click to collapse
Thank you. Yes, I read quite a lot yesterday and found out that I have followed the steps properly. So I am wondering if it has got anything to do with the boot.img from the PA ROM?
And yes I did a nandroid backup previously as well, however, I was not aware of how to restore it because I couldn't access the recovery mode. Can I do the restore using the FlashTool? or some other tool in such a scenario?
I downloaded "pa_togari-4.5-BETA1-20140805.zip" available in this link: http://aospal.hostingsharedbox.com/aospal/roms/togari/ . Should I try the last stable release rather than the beta one?
I am sorry for this noobish question, but what exactly is the purpose of "boot.img"? Is it the kernel of the new ROM that I am going to install? or is it something else? I kinda think that the problem might have been with the way I flashed the boot.img previously. I used the option "SELECT SYSTEM TO FLASH" under the fastboot of FlashTool in order to do so. Is it wrong? Should I use the "SELECT KERNEL TO FLASH"?
Thank you again
EDIT: I used the "SELECT KERNEL TO FLASH" option in the Flashtool, to flash the boot.img and I was able to flash the PA 4+ successfully! ..Thank you!
Prabash said:
EDIT: I used the "SELECT KERNEL TO FLASH" option in the Flashtool, to flash the boot.img and I was able to flash the PA 4+ successfully! ..Thank you!
Click to expand...
Click to collapse
Good to hear you got it sorted, but I'll run through what you did wrong...
Thank you. Yes, I read quite a lot yesterday and found out that I have followed the steps properly. So I am wondering if it has got anything to do with the boot.img from the PA ROM?
Click to expand...
Click to collapse
So you now know it wasn't the boot.img :laugh:
And yes I did a nandroid backup previously as well, however, I was not aware of how to restore it because I couldn't access the recovery mode. Can I do the restore using the FlashTool? or some other tool in such a scenario?
Click to expand...
Click to collapse
Normally the way to recover would be to flash a boot.img that works and then enter recovery rand restore, easy when you flash the boot.img correctly
I am sorry for this noobish question, but what exactly is the purpose of "boot.img"? Is it the kernel of the new ROM that I am going to install? or is it something else?
Click to expand...
Click to collapse
The boot image is the kernel and recovery backed into one (it's a Sony thing ) and it belongs on the /boot partition
I kinda think that the problem might have been with the way I flashed the boot.img previously. I used the option "SELECT SYSTEM TO FLASH" under the fastboot of FlashTool in order to do so. Is it wrong? Should I use the "SELECT KERNEL TO FLASH"?
Click to expand...
Click to collapse
I think you have figured that one out now :cyclops:. So what you did was write the kernel and recovery to the /system partition, not to where it belongs ie /boot
You can also use the "select kernel to boot (hotboot)" (or what ever words it uses) to boot a kernel/recovery and not change the one on the /boot partition - can be handy at times
I hope that helps you understand some bits about your new Sony ZU
Yep! thanks a lot for your help! Really appreciate it! :victory:

[RECOVERY] TWRP 2.8.0.0 for LG F70 D315

[DEV]TWRP RECOVERY FOR LG D315 F70​
Warning : This operation involves risk. XDA community or me can not be held responsible for any problems​
Hi everyone!
Well, Since this smartphone is somewhat forgotten in the Android community, I decided to work on it ! I unlocked the fastboot and ported TWRP Recovery for the LG F70 ! It works on the D315, for others I really don't know ... But since I did the porting myself it must be considered as an alpha version x ') The only problem is I had to use a theme for TWRP, because the default theme was too big for this phone :/ Well you might say, it is nice like that ! The themer is "z31s1g". Anyway. If some people want to test and give feedback, this is here ​
First, make sure your phone is rooted (you can do it with towelroot) and make sure you have the Android SDK installed, and the LG drivers.
Download my attachment and extract it on your computer.
Right now you have to activate fastboot, fastboot is hidden behind the download mode, so backup your download mode :
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
And now set zero the download mode with this command, then reboot :
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
adb reboot
Now you have replaced the download mode by fastboot. Let's start fastboot, to do so, you have to turn off your phone, hold Vol+ button and plug in the USB cable.
On the console, do this command to check if phone is connected and detected.
Code:
fastboot devices
There should be a random sequence of numbers, and "fastboot" displayed.
So now we will proceed to flash the recovery with this command :
Code:
fastboot flash recovery c:\PathToTheRecoveryImage\recovery.img
Then reboot with this command :
Code:
fastboot reboot
Done ! This is my first tutorial in english... I'm a 17 years old french user, excuse me if my english is bad x)
************************************************************************************
UPDATE HERE, BOOTLOADER UNLOCKED AND NEW RECOVERY
************************************************************************************
Thanks in advance if someone want to test it and post a feedback, I will make a little list of what's working / not working (I already tested it, I didn't see nothing right now Enjoy !
KuroHaki said:
TWRP RECOVERY FOR LG D315 F70​
Warning : This operation involves risk. XDA community or me can not be held responsible for any problems​
Hi everyone!
Well, Since this smartphone is somewhat forgotten in the Android community, I decided to work on it ! I unlocked the fastboot and ported TWRP Recovery for the LG F70 ! It works on the D315, for others I really don't know ... But since I did the porting myself it must be considered as an alpha version x ') The only problem is I had to use a theme for TWRP, because the default theme was too big for this phone :/ Well you might say, it is nice like that ! The themer is "z31s1g". Anyway. If some people want to test and give feedback, this is here ​
First, make sure your phone is rooted (you can do it with towelroot) and make sure you have the Android SDK installed, and the LG drivers.
Download my attachment and extract it on your computer.
Right now you have to activate fastboot, fastboot is hidden behind the download mode, so backup your download mode :
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img.
And now set zero the download mode with this command, then reboot :
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
adb reboot
Now you have replaced the download mode by fastboot. Let's start fastboot, to do so, you have to turn off your phone, hold Vol+ button and plug in the USB cable.
On the console, do this command to check if phone is connected and detected.
Code:
fastboot devices
There should be a random sequence of numbers, and "fastboot" displayed.
So now we will proceed to flash the recovery with this command :
Code:
fastboot flash recovery c:\PathToTheRecoveryImage\recovery.img
Then reboot with this command :
Code:
fastboot reboot
Done ! This is my first tutorial in english... I'm a 17 years old french user, excuse me if my english is bad x)
Thanks in advance if someone want to test it and post a feedback, I will make a little list of what's working / not working (I already tested it, I didn't see nothing right now Enjoy !
Click to expand...
Click to collapse
Hello, it seems that only me and you have this phone. So, I'd like to root my phone, do you think that I could use towelroot without risk?
I think I'll try your guide too... after root
Thanks in advance
Yes, you can use Towelroot, but for the recovery, remember it's only a first test, and I don't know if the bootloader is locked... but the recovery seems to work
good. towelroot works well and I have no problem since now. do you think I could install gravity box in this phone with stock rom? how can I unroot this phone? thanks in advance
It was not able to enter the Fastboot
Hi. I thank you TWRP who porting. I have not imagined and think you made using the TWRP in the F70 model. However Execution has not been in the loading screen of the download mode it is not possible that you have used the dd if = / dev / zero of = ~~ command as described in your article, but to enter the fastboot.
How can I do? I use F370s model.
I'm sorry. I use google translations...
d315
hi. also have the korean version of this phone. can i use international rom on this phone so that mine test isnt korean language?
---------- Post added at 03:47 PM ---------- Previous post was at 03:41 PM ----------
can someone confirm this
seventivi.blogspot.com/2014/10/upgradeupdate-lg-f70-d315-to-50-lollipop.html
mrteejay said:
hi. also have the korean version of this phone. can i use international rom on this phone so that mine test isnt korean language?
Click to expand...
Click to collapse
I think yes. I've Singapore's version of D315 and flashed a Hungarian D315 rom with no problem.
You can download some ROMs from 4pda F70 Flash thread.
rom
Thats freakin awesome. Can you guide me on how u accomplished flashing ur phone. So far im only rooted
mrteejay said:
Thats freakin awesome. Can you guide me on how u accomplished flashing ur phone. So far im only rooted
Click to expand...
Click to collapse
I've used this tool (this tool has a tutorial on its page). After flashing you have to root again.
Duble check to be sure that you have lg d315 model and downloaded lg d315 firmware!
This is the model of my phone. It didnt say it is d315. But i read it its the same only it is the korean version. See attached image. Should i go continue flash?and what is the consequence if i use different rom for my phone?
mrteejay said:
This is the model of my phone. It didnt say it is d315. But i read it its the same only it is the korean version. See attached image. Should i go continue flash?and what is the consequence if i use different rom for my phone?
Click to expand...
Click to collapse
There is no guarantee for a successful firmware flash.
What if flashing failed? Can i revert back?
mrteejay said:
What if flashing failed? Can i revert back?
Click to expand...
Click to collapse
If flashing failed you will have to disassemble a bootloader and to correct security checks inside.
So, It's possible but VERY hard.
Hi all ! I just worked on this phone night and day x)
I just unlocked the bootloader, and made a CWM port (I personnally prefer CWM x) ) And i'm working to make a port of Cyanogenmod 11, but i'm only 17 y-o and... Well, that's too hard for me x) I've compiled it, with bin blobs, and other stuff, all the config files, etc, but it's not working YET x) (If anyone want to help me I can share my project...) Well :
/!\ For Recovery to work, you MUST unlock the bootloader by this method, this is very simple (Thanks to Zaaap72) /!\
CWM 6.0.5.0 : CWM 6.0.5.0.img
Method to unlock bootloader (not by me) : http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
The G2 Mini (D620) Has the same architecture as the F70, I mean Qualcomm msm8226, Snapdragon400, Same amount of ram, etc, BUT, not the same screen... And I'm trying to adapt the cutom kernel, and sources of D620 CM11 for my F70 x) Again, If anyone can/want help me
(Remember that the recoveries I made are in beta-test, this is my first try, and I will update them in the future, If you find any bugs, tell me, or modify the .img by yourself with AIK and upload the image for me Thanks !)
Have a nice day guys
KuroHaki, what version of device (D315/F370), device region and firmware (v10a/b/c...) bootloader did you use to unlock? Zaaap72's unlock method is very risky and unstable solution. The best solution is on 4pda, Anyway you're done!
You can try to make a recovery image with LG-L70 recovery binary and F70 kernel. It may work, I've made like that before with MTK devices.
I have a v10b D315, and I used the 4-bytes method, on aboot and abootb, it awesomely worked I played with chance on this, and it worked x) If anyone want to test it on another firmware/model of F70... And for the Image, I don't need recovery, I need a Kernel that can boot Cyanogenmod, because the LG sources make my phone bootloop on the LG first logo... I tried with Zaaap port of Quarx sources, with no success... Kernel compilation is very hard for me, I had many errors with Drivers on Quarx source, I changed the files with errors with files from LG source, and It compiled, but not worked... I don't understand why... Well, if anyone have a solution for this kernel... x)
I am the owner LG F70 phones and watches this topic for a long time but did not move anything, whether it was by the opportunity to do any ROM for this device ?
Wow! Thanks for this Recovery!!!! Was looking a while for twrp on the F70! :good:
I did flash the recovery successfully with the method in the OP. However, when I reboot to recovery (adb reboot recovery) it failed to boot TWRP - a screen showed 'secure boot error' then there were was a dump screen with lots of drives mounted to my linux pc.
This is likely because I didn't unlock the boot loader right? However, the method provided to unlock looks a bit too risky - especially since I dont have a recovery to restore if the stuff break the system. Anyway, thanks for this!
@up
I don't think so the unlock bootloader it's dangerous. I have done files aboot and abootb so i can send you.
Russian LG bootloader guru Andrew-New from 4pda has made a patched bootloader for lg d315 from v10b aboot.bin as I've requested him.

[Q] Unable to boot on TWRP

My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
LucasBS1 said:
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
Click to expand...
Click to collapse
Sometimes booting recovery doesn't work...You will have to flash it. Perhaps you can flash the stock recovery after successful root? though i am not sure that will work
Also try booting into CWM
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
LucasBS1 said:
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
Click to expand...
Click to collapse
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
giaur said:
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
Click to expand...
Click to collapse
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
LucasBS1 said:
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
Click to expand...
Click to collapse
None of them worked. I'm going to resign, because there is nothing I can do. Seems you have exactly the same problem as me. What I tried:
- fastboot boot recovery.img. Phone hangs on bootlogo
- flash recovery, then use go to recovery option in fastboot menu. In this case, 2 possibilities: with usb cable connected, it boots normally to system, not to recovery. With usb cable disconnected, screen goes black and phone looks like powered off. You will need to power it on and it will boot to system.
- On running system with usb debugging enabled. If you type "adb reboot recovery", you will end with dead robot and "no command" error. You can however press VolUP +Power on this screen and you will see Android 3e recovery.
If you have the same problem as me, you are completly lost and it's impossible to intall recovery on your device. I'm close to resign and say "**** this ****ty phone" because (as you already mentioned), there is no any attention on my questions, twrp support was dropped long time ago etc.
Flashing recovery should not wipe your data, so once you try to flash twrp or cwm, please let me know about your results. I'm sure I will never able to solve this problem, but I will feel better knowing that I'm not alone whit it
---------- Post added at 06:05 PM ---------- Previous post was at 06:00 PM ----------
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
Still the same, I'm on stock recovery. In console, no errors:
Code:
[email protected]:~/android/DO_MOTOROLI/twrp/2.8.5$ fastboot flash recovery twrp2.8.5.0-recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (9046 KB)...
OKAY [ 0.312s]
writing 'recovery'...
OKAY [ 0.860s]
finished. total time: 1.172s
But "adb reboot recovery" - "No command". Damn it...
---------- Post added at 06:26 PM ---------- Previous post was at 06:05 PM ----------
Ok, I'm finished. It's not possible. F U C K Motorola and good night. My advice: don't waste your time if you have the same problem. You will get nothing, except wasted time. It's good that it's not my phone (I own OnePlus One). But I was asked to install CM12.1 on my friend's phone. It's impossible, so I will need to tell him I was failed with that.
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Seeing giaur on that situation puts me stepping back...
LucasBS1 said:
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Click to expand...
Click to collapse
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
giaur said:
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
Click to expand...
Click to collapse
Cool
Regarding to safety
Should I flash CWM or TWRP ? Why ?
Regarding the method
Flash through usb->Fastboot or through Apk (like CWM)
Or a third method ?
And why
Between TWRP 2.7 and 2.8, which one is safer ?
And of course...why ?
And a last question, before I leave you guys alone:
Did you manage to root the phone, despite the poblems occurring to you, giaur ?
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Yo !
Flashed TWRP
But wiped things I shouldnt
How to put the ROM back via USB ?
EDIT:
NEVERMIND
Found how to use SD to do that
giaur said:
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Click to expand...
Click to collapse
I was also struggling a lot many days into getting twrp and cw loaded on to a Moto E. The problem was that I was pressing the Power button to activate the recovery menu and that will not activate the recovery option. You got to press the UP button instead of power after executing
Code:
fastboot.exe flash recovery twrp-2.8.1.0-condor.img
. This is quite counter intuitive but described well in most posts, but as experts we assume up button is to go up the menu.
Sunish Issac

[F3112/F3116][TWRP][3.0.2-6][PORT] TWRP recovery for XA Dual Sim

Hi all,
I'm happy to share my TWRP 3.0.2-6 recovery, I ported it from the Elephone P9000. It's for Dual Sim only, please don't ask me for other models (Ultra inclued) I don't have enought time to build them all for now.
I think you just have to change the kernel with Carliv Image Kitchen to port it to your phone (never tested with this easy way), use my released recovery for your model as base for porting, same way for Ultra. Please report and share if working
In this version I fixed partition, you are able to backup and restore all 31 partitions ( except for Cache), all ext4 partitions can be mounted rw (be careful at what you are doing!!). And I applied a new theme (multilang).
Unlocking /data with password is not working.
Flash it with Fastboot.
Download:
https://mega.nz/#!9g53VJjC!1d3Aat3FMD9azFb6REFSj266sXkSI78tTetrZWZplQo
See you !
EDIT: Added screenshots
awww cant wait to try :good::good:
btw, do you have any tuts for building custom rom from the stock one?
caosugai said:
awww cant wait to try :good::good:
btw, do you have any tuts for building custom rom from the stock one?
Click to expand...
Click to collapse
No tuts for the XA, you can try some kitchens like "Assayyed kitchen" to edit the rom. Try guides for MTK devices (64bits) or CM/AOSP. But nothing is made for XA, use them as base.
i dont ask for specialized XA, just xperia rom in general
and can i use the same boot.img of xx.73 for the new rom xx.81?
caosugai said:
i dont ask for specialized XA, just xperia rom in general
and can i use the same boot.img of xx.73 for the new rom xx.81?
Click to expand...
Click to collapse
For Q&A other than TWRP 3.0.2-6 release it's here:
http://forum.xda-developers.com/xperia-xa/help/qa-t-template-thread-sony-xperia-xa-t3479938/page1
Thank you
Help...
rrvuhpg said:
Hi all,
I'm happy to share my new TWRP 3.0.2-6 recovery, I ported it from the Elephone P9000. It's for Dual Sim only, please don't ask me for other models (Ultra inclued) I don't have enought time to build them all for now.
I think you just have to change the kernel with Carliv Image Kitchen to port it to your phone (never tested with this easy way), use my released recovery for your model as base for porting, same way for Ultra. Please report and share if working
In this version I fixed partition, you are able to backup and restore all 31 partitions ( except for Cache), all ext4 partitions can be mounted rw (be careful at what you are doing!!). And I applied a new theme (multilang).
Unlocking /data with password is not working.
Flash it with Fastboot.
Download:
https://mega.nz/#!9g53VJjC!1d3Aat3FMD9azFb6REFSj266sXkSI78tTetrZWZplQo
See you !
EDIT: Added screenshots
Click to expand...
Click to collapse
Hi bro, how to boot into recovery on f3116, i use adb and button but i can't, phone restart and not boot into recovery.
ahero123a said:
Hi bro, how to boot into recovery on f3116, i use adb and button but i can't, phone restart and not boot into recovery.
Click to expand...
Click to collapse
HI, it will not boot to recovery if you have a stock boot
Download the rootpack for Dual Sim and flash the boot.img first.
Fastboot commands are:
"fastboot flash boot boot.img"
"fastboot flash recovery recovery.img"
without quotes.
Change the name of the .img if needed.

Categories

Resources