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....
Related
Greetings All Modders
I want to make a CWM Recovery for my phone. All those which are there for my Device Does Not Work.
When I Go into recovery, it just hangs on the logo.
My Phone is a Qmobile A5 which is a non-3G_5mp-camera Clone of Micromax A75 and Gionee 73 Phone
Finger Print is:
Code:
QMobile/gionee73_gb/gionee73_gb:2.3.4/GRJ22/eng.android.1334221311:user/release-keys
I flashed it via SP Flash Tools with CWM available for Micromax A75, but as I said, it doesn't go into recovery now.
I Humbly Request All Modders to Help me make a CWM for my Phone.
I am uploading a CWM Recovery I have made.
I DOES NOT WORK. So please dont flash it unless you have a working Recovery backup!
Please tell me what is wrong with the Image.
I have made it Using Boot image extraction tool on GITHUB via Ubuntu Linux 12.04 LTS 32Bit
If any more Info Is required please ask, I am awaiting your replies as are many other Qmobile users how want CWM for their Phone.
Thank You
PS: The Attachment Contains the Recovery I have Made and the BUILD.PROP of my phone.
BUILD.PROP
any one?
More interesting would be that you upload your ORIGINAL recovery image, and which processor you have...
That's the problem... my recovry go erased by the new recovery :/
Sp flash tool is downloading but not reading back... so I was not able to make a backup.
Its mt6573 650mhz processor
Sent from my A5 using xda app-developers app
If anyone has the original recovery please post here...
I have mailed Qmobile to provide the original recovery but I have no hope from them... so please provide original boot image and recovery image...
Regards!
can i have cwm for my alcatel tablet?
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
EDIT: Use the method described by minhdangoz94 below.
Alternatively, boot into fastboot by "adb reboot-bootloader" and flash recovery.img from fastboot
emperorsum said:
Hi I have created a update.zip for the Xolo Q1000 Opus using the recovery.img created by minhdangoz (from mobiistar)
I created the zip form the stock firmware zip of the Xolo Q1000 Opus.
I deleted all other img from the zip and edited the updater_script and placed minhdangoz's recovery.img in the zip file.
This should flash the recovery.
I will be trying this on my phone when i get it back.
Feel free to use it -> View attachment 2723912
P.S the recovery is in vietnamese. you can use google translate . I am hoping to start working on the code written by minhdangoz and convert this to english soon.
Click to expand...
Click to collapse
I already made English version
and TWRP working well.
I will update my thread and send them to you guys.
CWM + TWRP
I just udpated my thread
and I made CWM Recovery English and TWRP 2.7.0.0
Pls check it out my thread here: http://diendan.mobiistar.vn/threads/cap-nhat-cwm-recovery-tl-504q-fix-man-hinh-xoay.24032/
II. CWM Recovey English version
Download recovery image here:
Code:
http://tenlua.vn/cwmrecovery504qen-img-0e37e526e5086406/#download0e37e526e5086406
Download this tool
Code:
http://tenlua.vn/504qcwmv2rotate-zip-0e37e52ee60a6c06/#download0e37e52ee60a6c06
extract it and remove the recovery.img files (Vietnammese version).
Rename downloaded recovery image to recovery.img and put it into Tool directory
run install.bat
III. TWRP 2.7.0.0
Download recovery image here:
Code:
http://tenlua.vn/twrptl504q-img-0e37e526e5086405/#download0e37e526e5086405
Download this tool
Code:
http://tenlua.vn/504qcwmv2rotate-zip-0e37e52ee60a6c06/#download0e37e52ee60a6c06
extract it and remove the recovery.img files (Vietnammese version).
Rename downloaded recovery image to recovery.img and put it into Tool directory
run install.bat
what will be outcome of this??
i am stuck with mobiistar firmware on my xolo q1000 opus phone.
i want to go back to xolo
please help me some one
krus_xlfu said:
what will be outcome of this??
i am stuck with mobiistar firmware on my xolo q1000 opus phone.
i want to go back to xolo
please help me some one
Click to expand...
Click to collapse
You can revert to stock rom with my thread here
http://forum.xda-developers.com/showthread.php?p=52568782
minhdangoz94 said:
You can revert to stock rom with my thread here
http://forum.xda-developers.com/showthread.php?p=52568782
Click to expand...
Click to collapse
BRCM multidownloader is not accepting Xolo stock rom
krus_xlfu said:
BRCM multidownloader is not accepting Xolo stock rom
Click to expand...
Click to collapse
@minhdangoz94
I am having a confusion. which software is to be used?
BCRM Multidownloader or the CUI interface software you have made.?
krus_xlfu said:
@minhdangoz94
I am having a confusion. which software is to be used?
BCRM Multidownloader or the CUI interface software you have made.?
Click to expand...
Click to collapse
@minhdangoz94
On installing update it is giving following error message
" No file_contexts. This package is for 'q1000 opus' devices; this is a 'java'.
error in /sdcard/update.zip
(Status 7)
Installation aborted.
please help me. what to do now?
krus_xlfu said:
@minhdangoz94
On installing update it is giving following error message
" No file_contexts. This package is for 'q1000 opus' devices; this is a 'java'.
error in /sdcard/update.zip
(Status 7)
Installation aborted.
please help me. what to do now?
Click to expand...
Click to collapse
Which update.zip are you installing?
minhdangoz94 said:
Which update.zip are you installing?
Click to expand...
Click to collapse
I tried xolo stock rom and also kitkat. But both are giving the same error.
I have one more query, do i need to use "wipe data/factory reset" option first to load xolo rom on mobiistar?
I am having a xolo q1000 opus running on mobiistar software and want to revert back to xolo software.
Attention Xolo Q1000 OPUS owners..
never load mobiistar rom on xolo or else you will be stuck like me. u can not load any other rom on it later.
krus_xlfu said:
Attention Xolo Q1000 OPUS owners..
never load mobiistar rom on xolo or else you will be stuck like me. u can not load any other rom on it later.
Click to expand...
Click to collapse
but is the mobiistar ROM working?
Try this:
1. First see if you can still access xolo stock recovery. the new kitkat update is out so update that from recovery.
(to get into recovery read my post on this thread http://forum.xda-developers.com/showthread.php?t=2712481
2. If you can't get into xolo stock recovery but if you can access adb then get into fastboot by using "adb reboot-bootloader" then flash stock xolo recovery. (ask me if you need xolo stock recovery.img for the opus)
3. use new kitkat updat.zip from xolo site. and flash from xolo stock recovery.
P.S if you find an easy method to root the phone please share.
emperorsum said:
but is the mobiistar ROM working?
Try this:
1. First see if you can still access xolo stock recovery. the new kitkat update is out so update that from recovery.
(to get into recovery read my post on this thread http://forum.xda-developers.com/showthread.php?t=2712481
2. If you can't get into xolo stock recovery but if you can access adb then get into fastboot by using "adb reboot-bootloader" then flash stock xolo recovery. (ask me if you need xolo stock recovery.img for the opus)
3. use new kitkat updat.zip from xolo site. and flash from xolo stock recovery.
P.S if you find an easy method to root the phone please share.
Click to expand...
Click to collapse
Yes, Mobiistar is working on my opus.
i can access the stock recovery (my mobile is showing mobistar instead of xolo so i guess it is mobistar stock recovery)
although i have xolo stock recovery but i will still request to provide me another(may be my stock rom is bad)
I have the kitkat update (downloaded on 10th may)
today xolo site was showing two kitkat updates. please tell me which one to download.
i used vroot for rooting mobiistar.
on installing kitkat(downloaded on 10th may) it is giving the following error message " no file_contexts. This package is for Q1000 opus devices. This is a mobiistar touch LAI 504Q. Installation aborted."
Please help.
@emperorsum
Please reply. i am looking forward to you for help.
Touch CWM
This is Touch CWM Recovery based Carliv Touch CWM Recovery
Fixed AP Crashed issue
Fixed mount USB storage issue
I will update soon in my forum
http://diendan.mobiistar.vn
krus_xlfu said:
@emperorsum
Please reply. i am looking forward to you for help.
Click to expand...
Click to collapse
Firstly, note that the latest kitkat update for the Xolo Opus is the one mentioned at the top of the page. It's 294MB. The other update (16MB) is for the people who updated their phones with s010 version, which was bugged. The 294MB kitkat update.zip on the site now is the S011 version.
Link -> http://www.xolo.in/sites/default/files/Q1000-Opus-Update/XOLO_Q1000_Opus_KitKat_Update.zip
The stock xolo recovery provided by @kgarg on this thread is www.dropbox.com/s/vi4kl4qhz2ofipq/recovery.img and is confirmed to be working by @shubh971 on the same thread.
The device is not getting updated with the xolo update.zip maybe because of 2 things
1. The mobiistar recovery does not support the xolo ROM. in which case it is quite easy to fix by just flashing the stock xolo recovery from fastboot.
2. The bootloader is not allowing the flashing of the xolo ROM. in which case replacing only the recovery won't work.
If this is the case then you can do 2 things:
a. replace the bootloader and other partitions using the images stored in the new kitkat update.zip (using fastboot). This can be quite
risky so I recommend trying the next method. If you follow this method try to flash all the images from fastboot.
Then boot into recovery using the methods I described earlier and flash the xolo ROM. This time the device should detect itself
the Xolo Opus and it should update successfully.
b. The other method would be to use @minhdangoz94's CWM recovery and flash the kitkat update from the CWM which should allow
you to flash the kitkat ROM. I suggest you try this first. because then you'd be only replacing the recovery.
P.S to get to fastboot .. connect phone to computer and then use the command "adb reboot-bootloader" to flash the partitions use the fastboot commands to flash particular partitions. make sure that the .img files are stored in the same folder as fastboot.exe
Hope that helps.
emperorsum said:
Firstly, note that the latest kitkat update for the Xolo Opus is the one mentioned at the top of the page. It's 294MB. The other update (16MB) is for the people who updated their phones with s010 version, which was bugged. The 294MB kitkat update.zip on the site now is the S011 version.
Link -> http://www.xolo.in/sites/default/files/Q1000-Opus-Update/XOLO_Q1000_Opus_KitKat_Update.zip
The stock xolo recovery provided by @kgarg on this thread is www.dropbox.com/s/vi4kl4qhz2ofipq/recovery.img and is confirmed to be working by @shubh971 on the same thread.
The device is not getting updated with the xolo update.zip maybe because of 2 things
1. The mobiistar recovery does not support the xolo ROM. in which case it is quite easy to fix by just flashing the stock xolo recovery from fastboot.
2. The bootloader is not allowing the flashing of the xolo ROM. in which case replacing only the recovery won't work.
If this is the case then you can do 2 things:
a. replace the bootloader and other partitions using the images stored in the new kitkat update.zip (using fastboot). This can be quite
risky so I recommend trying the next method. If you follow this method try to flash all the images from fastboot.
Then boot into recovery using the methods I described earlier and flash the xolo ROM. This time the device should detect itself
the Xolo Opus and it should update successfully.
b. The other method would be to use @minhdangoz94's CWM recovery and flash the kitkat update from the CWM which should allow
you to flash the kitkat ROM. I suggest you try this first. because then you'd be only replacing the recovery.
P.S to get to fastboot .. connect phone to computer and then use the command "adb reboot-bootloader" to flash the partitions use the fastboot commands to flash particular partitions. make sure that the .img files are stored in the same folder as fastboot.exe
Hope that helps.
Click to expand...
Click to collapse
@emperorsum
on using adb reboot-bootloader and other fastboot commands either device was not found or it kept waiting for device infinitely.
i could not understand why. according to me drivers are installed. the broadcom multidownloder software discussed above in this thread always detects my mobile. if u have some additional drivers then please send me the links. if there is some other problem then please guide me.
krus_xlfu said:
@emperorsum
on using adb reboot-bootloader and other fastboot commands either device was not found or it kept waiting for device infinitely.
i could not understand why. according to me drivers are installed. the broadcom multidownloder software discussed above in this thread always detects my mobile. if u have some additional drivers then please send me the links. if there is some other problem then please guide me.
Click to expand...
Click to collapse
Dude... i now understand you only have mobiistar CWM.. lol.. i thought u had their whole OS... and u just want to install xolo kitkat.. right?
the gingerbread android on your phone is still xolo, right? do you have xolo care app on your phone? if you have you really needn't worry much...
but if you have mobiistar ROM then.. I will find a way.. I am just flashing my phone with the mobiistar ROM.. just for kicks lol.. i'll guide you once i find out how to revert back to XOLO
emperorsum said:
Dude... i now understand you only have mobiistar CWM.. lol.. i thought u had their whole OS... and u just want to install xolo kitkat.. right?
the gingerbread android on your phone is still xolo, right? do you have xolo care app on your phone? if you have you really needn't worry much... i'll help you out.. it's really simple problem you have.. haha.. i got confused sorry..
you just need to put stock recovery.. that's it.. i'll guide you... but confirm, first if what is said is right.
Click to expand...
Click to collapse
you got it half right. i think the picture needs little more clarity.
well.. to start with..
i have mobiistar cwm installed on my q1000 opus. my mobile does boot and works goods but the Jellybeen OS is from mobiistar and most of the applications in it are vietnaamese language.
Yes i want to install xolo kitkat. The android OS on my phone is from mobiistar.
krus_xlfu said:
you got it half right. i think the picture needs little more clarity.
well.. to start with..
i have mobiistar cwm installed on my q1000 opus. my mobile does boot and works goods but the Jellybeen OS is from mobiistar and most of the applications in it are vietnaamese language.
Yes i want to install xolo kitkat. The android OS on my phone is from mobiistar.
if you ever need to contact me then my number is +919235501998.
Click to expand...
Click to collapse
Ok.. My phone is now working on Mobiistar ROM as well.. I'll see if there is a way to bring Xolo back.. My brother has the same phone.. i'll ask him to send me the stock files and try... let's see... worst comes to worst - i am sure i can atleast manage to get a fully working English KitKat on the the phone even though it might not be from Xolo.. I'll let you know how it goes.. on this post... I'll also text you as soon as I find a solution... haha atleast now you aren't the only one with mobiistar on the xolo Opus.
Edit: I am using a temporary solution. your adb reboot bootloader is probably not working cuz of drivers. Dirvers try these drivers. they work. but u might have to manually replace the drivers in "Device Manager". what i did was, i made a back up of the system partition before i flashed the mobiistar ROM. now I used the CWM restore to restore the xolo ROM. I will upload the file.. it's www.xynocast.com/cwmbackup.zip . put the folder "clockworkmod" into root directory of your SD card. and boot into CWM. go to "backup and restore" -> "advance restore" "restore system". reboot xolo android 4.2.2 should boot. care though.. data might get lost
My device is philips s396 and without recovery it cant be rooted so need help in developing the recovery im agreeing to test it just give me the scatter file for flashing in mtk flash tool
gil65lg said:
My device is philips s396 and without recovery it cant be rooted so need help in developing the recovery im agreeing to test it just give me the scatter file for flashing in mtk flash tool
Click to expand...
Click to collapse
Find recovery for your processor.
unpack you stock boot and recovery
place your kernel in recovery from stock boot.
Pack ^)
Proffit.
Tool: http://rghost.ru/82v4pNC7Y
Without root the stock boot is not extractabale!
Hi. I just want to ask about TWRP recovery that is Compatible with my Phone :
Starmabile PLAY Click
Android 5.1 Lollipop
Spreadtrum SC7731
4.5"
Quadcore
Anyone with a Phone with same specs as mine that is using A TWRP ?
Please help. I wanna try yours.
Cant find on google with the same specs with my phone with twrp working.
I have tried those TWRP on google but none of them works. All of them take me Only to the Bootlogo. Only thing i know as of now is i have to port twrp to my stock recovery or to my phone.
Anyone please help.
maucerezo said:
Hi. I just want to ask about TWRP recovery that is Compatible with my Phone :
Starmabile PLAY Click
Android 5.1 Lollipop
Spreadtrum SC7731
4.5"
Quadcore
Anyone with a Phone with same specs as mine that is using A TWRP ?
Please help. I wanna try yours.
Cant find on google with the same specs with my phone with twrp working.
I have tried those TWRP on google but none of them works. All of them take me Only to the Bootlogo. Only thing i know as of now is i have to port twrp to my stock recovery or to my phone.
Anyone please help.
Click to expand...
Click to collapse
Hi Bro,
i have sc7731c (karbonn titanium 3D Plex ) device too. and i have tried many available img but none of them worked this would be because these devices are new and there no suitable recovery available simply because people have not made any till now..
There is many programs that allows u to create a new custom recovery if there is no recovery is available for your device try to goggle it.
On windows, philz magic touch recovery tool, android kitchen recovery image unpacker and so on.
Can i make you custom recovery using your stock image if you're too lazy
as i said above i have been trying to flash online available recoveries and accidentally flashed my stock u could help me out this
can u provide me you stock recovery image file ?
@Maucurezo
Hey dude! Im a pinoy. Im running with my STARMOBILE PLAY CLICK. As same as yours. Im running on the same Spreadtrum SC7731C and I flashed a Custom Recovery but it would only bring me to bootload. I kept finding solutions to get my Stock recovery but failed. We have the same Problem. I need the Custom recovery too. Help us admins
You can try and do it yourself. Porting TWRP and CWM to a new device. You'll need the stock rom for your device or simply make an image "dump" of the system files (boot.img, etc) via adb. Goodluck.
TWRP for sc7731c hope it helps
hi all a have a sc7731c phone on android 6.0 and i was able to install twrp on my device
it all started when i found a stock rom on the web (Google your device for stock - rom or - firmware)
once i had the rom i started searching for a way to extract the stock recovery from the rom
and i found this tool SPD_Upgrade_Tool_R4.0.0001 using this tool i extracted my stock
recovery from the ROM ( recovery.img ) , first stage complete i had a stock recovery
taken from a rom for my phone - brand and model must be right on the stock
firmware/rom or you risk damaging you phone (DO NOT CHEAT PLZ)
ps:wen you unpack the firmware/rom you should get a .pac file
ps:finding my stock rom took me several days of search.
now for STAGE 2 i had a stock recovery a needed to change it
for twrp another few days of search i came across a site
called hovatek here i found a tool to port (change) the
stock recovery to boot the twrp recovery the tool name is
[Hovatek] Spreadtrum (SPD) Auto TWRP Recovery Porter V1.0 by Team Hovatek (x86)
i run my stock recovery with this tool the tool creates a modified recovery on the
output folder( a few kb bigger ) stage 2 done.
STAGE 3
1- a fully working ADB, for this your best option is android-studio
2-turn on USB debuging and OEM unlock in DEV options
3-name the new recovery file recovery.img
4-your device has to be in USB MTP mode
5-if ADB is properly installed and Windows has the correct android device
driver you should be able to use these commands using android-studio's ADB
command-adb devices
-if the device is detected a serial number apears
command-adb reboot bootloader
-the device reboots to a black screen with small white letters saying FASTBOOT mode
command-fastboot devices
-the device displays the serial number again
command-fastboot flash recovery recovery.img
- if all went well it will say successful
command-fastboot reboot
-dont remenber if it booted straight to twrp or if i had to use power + volume up
-by the way on my phone to get in the default recover its 1 second hold power
and then with the power pressed for 1 sec add volume up 3 sec and let go of both
any way it worked i hope it helps ppl with these sc7731c phones
i have twrp 3.0.0 fully working
tips: youtube vídeos on how to use SPD_Upgrade_Tool_R4.0.0001
the hovatek site has a great tutorial on how to use the recovery porter tool
the last part the ADB commands was a ***** as Windows did not install my device
correctly and this is crucial -install phone driver manualy/Google device/Google android device. good luck
ps: all merit goes to the developers of these tool, a great ty to them :highfive:
ps: at the start i did NOT have root, the success flashing the ported twrp recovery
was followed bi the installation of the magisk15.3.zip and voila twrp+root
any one help me i port twrp using adb but after i flash my twrp upside down on sc7731ceb it works fine but the twrp upside down any help me
pauljack2 said:
any one help me i port twrp using adb but after i flash my twrp upside down on sc7731ceb it works fine but the twrp upside down any help me
Click to expand...
Click to collapse
humm,.. as far as i now adb does not port recovery image´s you mean you found an image for sc7731?? phone and there are at least 4 or 5 variations of the sc7731 board and you
flashed it on your phone, by shear luck you did not soft-brick or brick your phone and it actualy Works, :cyclops:
you need to search Google/xda/hovatek site for your brand and model´s stock recovery or even better your custom recovery
or as an alternative your stock ROM/FIRMWARE and then extract the stock recovery from ROM/FIRM port it and flash it
im prety shure someone out there has a phone like your´s and you can , when you find it download the stock recovery - the custom recovery - or the ROM/FIRMWARE file
the hovatek site has a great auto port tool all you need is your stock recovery follow the vídeo simple steps and flash it now that you have root just use
twrp oficial app to flash it ,se my tutorial above it will be easy once you have the stock recovery or rom/firmware
i have a 50 buck cheap phone wierd brand,it took me several days to find the stock rom/firmware once i did all worked just fine no strange stuff
hovetek site also has a lot of rom´s/firmware files for many brands and model´s , again search Google/xda/hovatek for your model + stock recovery or recovery.img, custom recovery.
good luck
i have stock recovery so i copy the recovery from my stock and i use carlivimg so i can unpack my recovery.img but i have really problem on upside down but i work fine i flash supersu on it now i have rooted my phone. my phone by the way is ding ding defi go SC7731ceb i use TWRP 3.0.2.0 it works fine but if you update the latest twrp you have problem on failed mount and .etc
ANY can help that upside down ??? thats my problem now on my recovery
but you can port recovery using fastboot
i commend
c:/adb>adb devices
adb>adb reboot bootleader
adb>fastboot flash recovery recovery.img
thats i port my recovery on sc7731ceb
using pc
pauljack2 said:
i have stock recovery so i copy the recovery from my stock and i use carlivimg so i can unpack my recovery.img but i have really problem on upside down but i work fine i flash supersu on it now i have rooted my phone. my phone by the way is ding ding defi go SC7731ceb i use TWRP 3.0.2.0 it works fine but if you update the latest twrp you have problem on failed mount and .etc
ANY can help that upside down ??? thats my problem now on my recovery
but you can port recovery using fastboot
i commend
c:/adb>adb devices
adb>adb reboot bootleader
adb>fastboot flash recovery recovery.img
thats i port my recovery on sc7731ceb
using pc
Click to expand...
Click to collapse
Go here https://forum.hovatek.com/thread-21669.html try and port again with this tool it worked fine for me.