yashsingh1/xdaforums huggingface dataset:
[Android General] anpr22:
I ported twrp recovery meant for sc8830 and used fastboot boot image-new.img. The cmd screen says success in downloading and booting but my phone's screen just show logo with fastboot mode. fastboot devices give some serial no. and fastboot oem device-info fails.

My phone is Trio selfie3 t45, device is scx35_sp7731geaplus_dt, cpu hw is sc8830, rooted and philz custom recovery working with lags and missing sequences.

Please help.

---------- Post added at 07:35 AM ---------- Previous post was at 07:30 AM ----------

The miracle box method gave error code 1 after connecting with the port.

the second method did not work as back up files were not created due to .sh file having /proc/mtd which is not there on my phone.

I asked it there but the response is very slow unlike here.

Thanks I will wait !
[Android General] Jitheshwar:
You are supposed to use another command to boot into recovery not sure but the command for booting into recovery is "fastboot reboot recovery <recovery name>"

Use flashify for flashing recovery you can reboot to recovery from flashify itself tap the dot menu in flashify and then tap on reboot recovery option alternatively​you can use advanced reboot menu app from play store.

I think you don't need to create .Pac you restore the backup from fastboot by using command "fastboot flash system system.img" (without quotes).
[Android General] anpr22:
Wow and thanks, I really don't need .Pac or like if I can restore my phone using fastboot. but there are some queries.

1) At present I can use "adb reboot bootloader" to go into fastboot mode. Suppose if I have bricked my phone then connecting usb cable (suppose debugging on before brick) how to access fastboot mode? Will it be accessible ?

my vol up + power key takes me to recovery, volume down+ power takes me to test mode, volume up + volume down connects port to miracle box but not fastboot mode. so will it work ?

2) Also, what files I need to flash for full restore supposing I backed up all , is the partition name same as name in img ?

3) I am willing to use flashify but only when i know i can flash stock recovery using fastboot without doubt if it bricks. I tried fastboot boot stock-recovery.img also for testing and it again downloaded and booted successfully only on cmd but not on phone screen. (edit- By the way I read new command is fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img where "lge.kcal=0 ...." is a kernel command line. may be you can help me how to know kernel command line.)

I will let you know how " fastboot reboot recovery recovery.img" goes ?
[Android General] Jitheshwar:
1) There might be different key combination to enter into​ fastboot mode. Once I tried to boot into fastboot mode for my spreadtrum phone using key combo but failed and I have other phone which is having Snapdragon chip in it I have successfully entered into fastboot mode I think for spreadtrum phones we can enter in only two ways into fastboot mode either by using adb commands or through recovery (some stock as well as custom recoveries are having option for booting into fastboot )

I gave a link and told you to try temporary recovery have you tried it? Let me know. It works pretty well and it's having option to boot into fastboot mode. I flashed many ROMs using that temporary recovery (it was some months back but now I am having TWRP recovery)

2) What files to be restored will depends on with what system files you messed up. For example if you modified files in /system partition and this resulted in bootloop then restore the system backup. In most if the cases we will modify system,boot and recovery only so if you want to fix bootloop then just restore system and boot this is sufficient no need to restore imei and modem unless you faced any issues like sim is not detected and imei no. Is showing null after restoring system backup.

3) In my view flashify is much safe to use because I never faced any issues with and it is even easy to use and saves much time. You will not brick your​device just by using flashify provided that you use it for flashing recovery only do not touch the boot partition at any cost if you incorrectly flash recovery.img to system partition obviously you'll end up with bootloop.

I don't know much about fastboot because I used it only once that is only to flash custom recovery to get root access.

I suggest you to Google regarding fastboot you can find lots tutorials and also use XDA search plus for getting info.
[Android General] Jitheshwar:
Since you are having working custom recovery you create stock ROM flashable zip. And then use the files contained in stockRom.zip for porting ROMs from other devices with same chipset

Steps to create flashable​ zip of stock ROM :-

1) Requirements

"Partition backup" app from play store

ZArchiver from play store

META-INF folder containing updater script having same mount points that you are having

2)Choose boot and system partition for backing up

3)choose raw image backup for backing up the boot and system make sure you have at least 2GB of space in the disk you going to take backup

4)Open ZArchiver and then navigate to system.img(raw partitions backup taken using partitions backup app in step3)

5)Rename system.img to system.Zip

6)Then tap on system.zip and then choose this option " extract to ./<Archive name>/"

7)Now you'll see all folder contained in system partition in system folder

8)Select META-INF​ folder, system folder and boot.img and then compress all three files to zip(select compression level as normal)

9)Now you'll see see your stock ROM.zip which should appear as shown in the screenshot

Bonus: for getting META-INF folder download any custom ROM of KitKat device from this thread https://xdaforums.com/android/general/kitkat-rooting-to-roms-t3560777
[Android General] anpr22:
Okay thanks, I will do that. Please suggest me a nice custom rom for 512mb ram and 4gb internal memory(1 gb usable) .
[Android General] Navjot Sherry:
check this out bro

https://xdaforums.com/android/general/8gb-intex-aqua-star-28gb-root-install-t3615573
[Android General] nalas:
Recovery for Lava A68 SC7731G

Hello.

I've tried to port TWRP recovery to Lava A68 Spreadtrum chipset SC7731G with no success - black screen, stuck on logo, no working keys , no working commands :(.

Android 6.0.1

Can You help me to port this?

Below is stock recovery for this model - big thanks.

View attachment 4168893
[Android General] kaew158:
Recovery for Lenovo A1000 SC8830 Android 5.0

Hello.

I've tried to port TWRP recovery to Lenovo A1000 Spreadtrum chipset SC8830 Android 5.0 with no success - black screen, stuck on logo, no working keys , no working commands . I try to flash many twrp files for this device have same problem.

Can You help me to port twrp for this device?

Below is stock recovery for this model - big thanks.

Lenovo A1000 stock boot & stock recovery
[Android General] Jitheshwar:
Bro there is working TWRP for A1000 out there in the dedicated group (at Facebook) for Lenovo A1000. Search on Facebook using your device name you'll find the group after that become member and then download desired files from the files section. Since you are not a member I'll give the link of TWRP you can find it here
[Android General] kaew158:
All files make me stuck logo boot screen.

Can you port twrp for me?

Stock boot & recovery

https://www.4shared.com/rar/5tMcgSyXei/A1000.html
[Android General] Jitheshwar:
How did you flashed recovery? Flash the recovery using flashify (if you have root access)/fastboot. Other apps may work this is suggested. Here is the group Official Lenovo A1000 Indonesia. Goto to files section and then download proper files and make sure there are no errors while downloading.
[Android General] kaew158:
My device is rooted and flash with flashify apk.
[Android General] Jitheshwar:
Ok then. I'll port for you. In the rar file that you given the link to me there are three different folders containing the boot and recovery with different build numbers so tell me which is your build number or take a backup using flashify app ZIP the backup and then upload it here (I suggest you to upload the recovery backup).
[Android General] kaew158:
I have three devices with three builds.

I backup them with Partition backup apk.

Please port only S100 with new link below and let me know to port other builds because I am not success to unpack recovery image with AIK apk , Carliv or Android Image Kitchen.

Thank you

A1000 S100 use flashify.

https://www.4shared.com/rar/qFOop4BZca/A1000_S100.html
[Android General] deanissd:
Do you have the firmware please? Could you send it to me I would really appreciate it.
[Android General] Salcykhan:
Spreadtrum

SC9830A

Twrp img fir this chipset (tested)

http://www.mrhhacking.com/2017/04/custom-twrp-recovery-for-lyf-flame-7.html?m=1

---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------

Spreadtrum

SC9830A

Twrp img for this chipset (tested)

http://www.mrhhacking.com/2017/04/cu...ame-7.html?m=1
[Android General] VictorVictor Tripura:
Does sc7731 custom recovery will support in canvas spark 3 q385??
[Android General] Jitheshwar:
If your device has the same spreadtrum chipset then yes. But you need to port it.

This thread is too old lot of things were not updated here I suggest you to look at this thread. Follow the guide available there to port the recovery.
[Android General] wdthompson:
Hi

maybe you can help,, I've been tearing my hair out trying to understand how touch works,,

the phone is a sc7715,, True smart touch 3.5. When I look at input0 I see ft5x0x, and clearly touch is working

I can flash a modded twrp to recovery and have no touch,, init.recovery.board.rc says on cali

insmod /system/lib/modules/focaltech_ts.ko,, I changed to on fs,, maybe should be post fs?

but this file does not exist??? I have not been able to explode zImage to see if the focaltech module is compiled in

Thats the only thing I can think gives the working touch in system, but md5 says that the zImage for boot and recovery are identical

And grepping for input,, uevent.rc seems to set it up, I duplicated that

With my setup, have to use sudo fastboot, it will not boot a recovery image, says dowload OK, booting OK, nothing happens

Even tried splitting it up , zImage and rd,, again said OK twice, but nothing happens (except fastboot dies, no more device)

I hope this is understandable
[Android General] smzubair:
Thankx

First I try #9, #1 and #2 nothing werks but #3 works like a charm. Thankx

Now I'm searching for ICS Rom for this old SPRD HSDroid Yoord AF5566 phone its now Gingerbread but it shows 4.0 in about.
[Android General] wdthompson:
Replying to myself,, I find by searching zImage that focaltech is indeed compiled in, I was using the wrong kernel

So, now my twrp mostly works OK, except for sdcard access, have to manually mount after boot

I have to find out how vold managed storage works
[Android General] Jitheshwar:
Recoveries and ROMs in this thread are too old port recoveries and ROMs from this thread.
[Android General] theanik:
I have a Micromax Canvas Mega 2 running Marshmallow with SC9832 chipset, can i use any of the recoveries above?

Also, I don't have root. Nothing worked so far. :(
[Android General] shekhar4u:
Take recovery for sc8830 and port it as discribed in the thread from above quote.

Flash it via fastboot.

Search chainfire su.zip

Install it via recovery.
[Android General] wdthompson:
Hi Jith

I checked out your link, I can't use any of these recoverys,

many have msg2 touch, many too big (>12M)

My phone (True 3.5 ,, 7715) has a 320x480 screen, ft5 touch (focalTech)

Thanks for the thought
[Android General] Jitheshwar:
Bro are you trying to tell me how to port recoveries and root? Have you read my post? I was trying help other member, I'm not seeking help from other member. Helping is okay, but read once before posting.
[Android General] shekhar4u:
:) Hi don't take it too seriously.....

I was just quoting your given link....for someone else.

Its late night glitch.

Well I have read all the post.
[Android General] Jitheshwar:
Link will not work in quoted post. Click that link and then copy it from browser and then paste it.

---------- Post added at 06:46 PM ---------- Previous post was at 06:37 PM ----------

The size of the recovery will be based on the size of the kernel. Those recoveries were made up of some other devices kernel (zimage) when port it the size of the recovery will be changed according to the size of stock recovery. And for the screen size recovery will be automatically gets adjusted to your display size (I guess because of the stock kernel it's possible). I don't know what is msg2 touch. Anyway give a try on all recoveries they may work.
[Android General] shekhar4u:
https://xdaforums.com/android/general/kitkat-rooting-to-roms-t3560777

Take recovery for sc8830 and port it as discribed in the thread from above quote.

Flash it via fastboot.

Search chainfire su.zip

Install it via recovery.
[Android General] wdthompson:
Hi Jith

>. I don't know what is msg2 touch. Anyway give a try on all recoveries they may work.

Tried the ones with ft5 touch, nope

I use abootimg to expand an image, then

strings zImage |grep -i (whatever),, touch, ft5, good, msg2,, various ts drivers compiled into kernel

Obviously the hardware and driver must match for the i2c communication to work

I think you are suggesting to replace the zImage with one from my hardware?

It is 7.0M, the bootimg.cfg also has to be modified (and updated) "bootsize = 0xc00000" (=12M)

Of course it all has to fit, or abootimg complains

But you see, I have a perfectly good twrp 302, except for no sdcard, I consider it

a learning experience to see how a perfectly good system has been screwed up

There is not very much info out there on new style vold, even tho its been out 2 or 3 years,

I am mostly referring to fstab.hardware entries, where do you stop?

where there is a device link, a driver link, or size,start,partition entries?
[Android General] wdthompson:
And a follow up, FWIW

I still haven't bent vold to my will, but I see

/etc/twrp.fstab seems to over-ride vold, especially if you add dirs to the image

Anyway twrp sees my sdcard as storage and the ext4 partition too

vold tries to mess it up, unsuccesfully
[Android General] Jitheshwar:
Are you digging through the zImage of recovery for fixing things? I think that won't help. Porting means just using the stock ROM kernel (which will helps to boot the recovery) with Ramdisk in excess we can change the fstab values. If you got a problem and unable to fix it there is only thing we can do is to use another recovery unlike ROM porting we can't do much while porting recovery (as far as my knowledge is concerned). The last option is to build from source to do it you need sources of your device. Apart from these I don't know much about these things because I ain't a dev but an advanced user ( I think I can add it). Also I don't have as much as knowledge you do. All I do is trail and error. Will you please me tell me how do you able to look it things in zImage and see what drivers were compiled with the kernel etc. I didn't find things like these(I think I didn't looked properly) but I need to learn these things.
[Android General] @ki:
First of all ......you can't see what is in the zlmage......not by any .....means........and if the recovery is booting.......then its easier to solve the mount point problems.......grab the log generated by twrp and you will find the error......:good:;)
[Android General] wdthompson:
Hi Jith

>Will you please me tell me how do you able to look it things in zImage and see what drivers were compiled with the kernel etc.

quite simple,, strings zImage,, run it thru grep,, "strings zImage|grep -i touch",, or focal or ft5 or good or msg2

These are all ts drivers, there will be some string reference to the particular driver that zImage uses

If you grep for "msg" you will get dozens of false positives, but msg2xx is a ts driver, in about 1/2 of

the twrp zImages (that you listed in post 1). the first 2 are focaltech, then a good, rest msg2xx

I just do this to know whether to even bother to try, the True phone has ft5x0x ts hardware

the twrp that I succeeded in booting had no twrp.fstab, that was the problem, now solved

---------- Post added at 12:14 AM ---------- Previous post was at 12:06 AM ----------

I have to wonder if you have ever used linux or grep?

Even grep will tell you if the string is in a binary,,

something like "binary file filename matches"

Of course strings will display the strings in a binary file,

you may wish to use strings -8 or strings -10 to reduce the output
[Android General] montanabay39:
cwm-recovery-SC7710g.img

Hi. am looking for this file cwm-recovery-SC7710g.img if you have it..or have an any ideas where i could find it would be appreciated.
[Android General] emonabin:
bro can u post that working cmw..coz i also have same problem like u had so maybe that will work for me too..thnz in advance :)
[Android General] kirito9:
i will look for it. hopefully before tonight i will post it :good:
[Android General] kirito9:
[MENTION=5756899]emonabin[/MENTION] the working cwm recovery
[Android General] emonabin:
thanks
[Android General] Sp0wL:
Please CWM for Blu Dash 5.0 D410 (recovey.img) for MobilUncle for Android.
[Android General] kirito9:
Your phone has a mediatek SOC....mt6572 which means if your phone has root i can provide a recovery for you once you give me the boot.img or stock recovery.img. Also in order to get those files your phone must be backed up. Here's the link to do a full backup of your phone http://xdaforums.com/showthread.php?t=2195780
[Android General] alb1us:
Orro 5c iphone clone

Hi, I tried all of them but none of them worked on my orro 5C iphone clone spreadtrum device!

I always get a blank screen.

Attached is my phone's original recovery image.
[Android General] alfahd:
if i flash recovery and try anther one , will not damage the system when i test many of these recoveries?
[Android General] designjeevan:
well, I created my own cwm from here:

theandroidhow.com/2014/04/flash-clockworkmod-cwm-recovery-any-mediatek-android-device.html

I am satisfied.
[Android General] kumbhakarnaraj:
recovery

need recovery for Spreadtrum SC6820
[Android General] aaron1108:
ureka

will this work on cherry mobile snap?

in either cases i will still try it

ahahahhaha lols
[Android General] tittilvero:
Lenovo A396 (Spreadtrum SC8830A) Android 2.3.5 Gingerbread Custom Recovery

Hi all!

Is there any chance you can help me finding a custom recovery that would work on my lenovo A396 (Spreadtrum SC8830A) and guide me through its installation?

I'd follow the tips in the first page of this post but my phone has Android 2.3.5 Gingerbread installed and it's incompatible

with Mobileuncle MTK Tools.

Any ideas?

Thank you very much in advance!
[Android General] brunoj16:
Help

Hello , no work on my phone ( SC6820 | Lumia N920 Copy ) , what I do? Some are with black screens , A7100.img turns white. Thank you.
[Android General] thedevilashish:
You may try others :) if none works then you will need to modify recovery.img ;)
[Android General] thedevilashish:
You need to build a recovery on your own bro ;) there are alot guides available for porting recovery!
[Android General] thedevilashish:
Try all of these! Any one may certainly work
[Android General] brunoj16:
Thanks for answering , I've tried them all and it did not work :(

My phone:

i.imgur.com/SlaHgUu.jpg

i.imgur.com/Y4jaaJy.jpg

i.imgur.com/u49zNoo.jpg

I used the MobileUncle Tool and the adb fastboot for recovery.img upload, and nothing...

Infos:

SPRD SPHS ON HSDROID (MODEL N920)

SYSTEM OS VERSION: ANDROID 4.1 (its false, is android 2.3)

CPU CORE: SINGLE CORE

CPU FREQUENCY: 1000 MHZ

RAM: 222MB

ROM:156

FIRMWARE: MCORDROID 2.3.5W12.20_P20.01
[Android General] thedevilashish:
There are alot of tutorials to build cwm from your stock recovery ;) try that!
[Android General] brunoj16:
My stock recovery is another and does not work. I do not have that came from, to make matters worse my situation =S
[Android General] Jitheshwar:
Sorry I don't have knowledge about Linux (not even basic).
[Android General] @ki:
No i have never used grep......and yhe thing you are talking about is nearly.... Impossible........as the zlmage is the compiled form ......you cant see the things........ Without having the source code......... ........i wish you success.......but this hit and try won't be easy

---------- Post added at 02:53 AM ---------- Previous post was at 02:51 AM ----------

With the advancement of the android version......it will be more difficult to see the things in zlmage.......i remember........when earlier android zlmage were extractable.......but.....that was gingerbread..........i suppose you are on kitkat.....or lollipop.........its impossible.......

Sorry if i demotivated you
[Android General] thedeviltauisf:
lava a79

hii guys

I am new user

so can any one gives a lava a79 custom ROM

any body

plllzzzzzz
[Android General] wdthompson:
Well, you know that the underlying OS on your phone is linux??

root@hy602:/ # ls -l bin/grep

lrwxr-xr-x root shell 2015-03-31 06:13 grep -> toolbox

root@hy602:/ # ls -l bin/strings

-rwxr-xr-x root root 1072136 2017-09-07 00:53 strings

This in an adb shell,, for android strings use -n <number> for string length

It is a very rare binary that have no strings inside, I've only seen that in compressed binaries

That strings,, above, is from busybox , I don't remember the version, they all have it
[Android General] @ki:
Well......ok..as you wish.....try yourself and find out

Chill:laugh:
[Android General] thedeviltauisf:
custom recovery

success full ported recovery and flashed but it goes in recovery but not touch or operate nothing happen
[Android General] Jitheshwar:
This is because of zImage(split-img) issue. Which is a kernel to boot the recovery which contains the hardware specific code and core hardware drivers. If there is no touch driver compiled with recovery by manufacturer then probably ported recovery's touch won't work. Anyway try some other recoveries if no luck you should use non-touch recovery.
[Android General] wdthompson:
@ki

>First of all ......you can't see what is in the zlmage......not by any .....means

>Well......ok..as you wish.....try yourself and find out

For your education,, the first statement is wrong, and I've told you why allready

2nd,,I do that nearly every day, thanks for the encouragement

[MENTION=8582957]thedeviltauisf[/MENTION] Have been following the above conversation,,

do you know what ts driver your phone uses?,,

do you have a copy of your phones stock zImage?,

is your phone rooted?
[Android General] thedeviltauisf:
yes sir my phone is rooted.

sir give me a non touch recovery. thanks
[Android General] theanik:
Sorry to disturb again. I ported recovery and flashed it. It worked perfectly, but when i flashed supersu, i got an /data mount error.

after rebooting, i got a bootloop. having no option, i reflashed to stock.

:\ did i miss any step? could you do it for me? i can provide my stock recovery....

Thanks a lot in advance

I have SC9832 btw.
[Android General] @ki:
see the twrp.fstab file of your twrp recovery ......match accordingly to your partition names
[Android General] theanik:
Will I match everything?

Like, from the stock recovery.fstab, I'll see what partitions are there and copy paste their addresses to the addresses in TWRP.fstab? the recovery iam using to port has both recovery.fstab and TWRP.fstab...to which one should i copy the partition addresses?
[Android General] @ki:
both i think
[Android General] Jitheshwar:
The TWRP will ignore recovery.fstab by renaming it to .bak and loads only TWRP.fstab mount points by renaming it to recovery.fstab technically we don't need recovery.fstab
[Android General] @ki:
thx for correction......
[Android General] theanik:
Can someone port TWRP/CWM for my Micromax Canvas Mega 2 running android marshmallow 6.0, which is not rooted. I tried porting a TWRP but touchscreen did not work. I want to root this devices from custom recovery using SuperSU.zip.

But I can't get any custom recovery for this device. Can someone help me out. D:
[Android General] Jitheshwar:
Detailed guide on porting recovery