[search] Factory Image 6.0.1 - LG G Watch

is it available

Yup here: system.img Have backup of original boot.img somewhere but it sucks ass so just use @invisiblek 's one HERE Also stock recovery kinda useless so just use TWRP from my rooting guide cause latest official TWRP can no mount squashfs HERE

thank you a lot and the other stuff is right about the custom recovery

Related

[RECOVERY][bacon] Unofficial TWRP 2.7.1.0 [7-13]

Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Recovery flashable version here
Credits: Dees_Troy
dr87 said:
Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Mount and unmount issues *may* be fixed (I haven't been able to reproduce them)
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Credits: Dees_Troy
Click to expand...
Click to collapse
Awesome job bro! Running like a champ!!
Sent from my One using XDA Premium 4 mobile app
Thanks a lot!
Now I can run Mahdi without problems!
thanks for this- but it's still not working- will i need to reflash madhi? i just fastbooted the recovery across and it boots into the recovery no worries and recognises all partitions but rom won't boot...
***edit*** it just booted up, about 5th attempt.. no boot animation though...ignore me...
Flashed recovery.img, bootet into recovery, no partitions..
Klarooo said:
Flashed recovery.img, bootet into recovery, no partitions..
Click to expand...
Click to collapse
Which rom were you running when you rebooted into recovery?
Stock, so CM11s.
mine still is not good. i treid to reboot to get it to hold the no hardware buttons. didn't reboot. tried about 10 times. eventually booted intot this new recovery and reflashed rom and booted it up. it's a bloody weird looking boot- no boot animation- made me think it was screwed again.
did you have to do anything to get it working again? Wipe entire device or just data partition?
Working good here, but I had no issues with the official build. I have an international version, 64GB OPO.
It's nice to see some additional features added, though.
Just helping out, packaged in a flashable zip for those with current CWM or TWRP recoveries, tested and working, enjoy everyone.
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Chris123NT said:
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Click to expand...
Click to collapse
Guys i wonder when you press efs restore is it
fastboot format modemst1 & st2
or
fastboot erase modemst1 & st2
or may be both? in that case in what order?
I flashed the one in OP, but the system does not see any partition ?
Can I flash 15th without bricking the phone
[EDIT] I tried a second time, and now it´s ok, partitions are there and backup is currently running
Any chance at adding F2FS support direct for this recovery for the ONE Plus?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Looks like the official .img version has been incremented to 2.7.1.1
More here: http://techerrata.com/browse/twrp2/bacon
A flashable zip for v2.7.1.1 would be nice.
Changelog? Hopefully they fixed those Partitions issues
2.7.1.1-Bacon Recovery Flashable zip
Mikey said:
2.7.1.1-Bacon Recovery Flashable zip
Click to expand...
Click to collapse
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
playya said:
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
Click to expand...
Click to collapse
Correct, easy huh
Delete the twrp.img......drag and drop the new img into the zip......dont uncompress the zip and compress it again.

[Help][LP 5.1] Needed boot.img for 'stock recovery backup experiment'.

I am going to do an experiment(flashing TWRP.img on boot partition and trying to root.) to backup stock recovery.img of Lollipop 5.1. To do this, I need stock boot.img(Kernel Version: 3.4.42-gccbac57) of system version 23.26.2. If there's someone who rooted system version 23.26.2 then take backup of boot.img using Rashr App(Download from here forum.xda-developers.com/showthread.php?t=2334554 ) and post that stock boot.img here.
If this experiment succeed then I will post stock recovery.img of lollipop 5.1.
UPDATE: I'm not going to do this experiment because temporary booting of twrp is now working on moto e. We can root device by temporary booting twrp and backup stock recovery.img
isn't there anyone who rooted 23.26.2 ?
I have 23.21.34 version i can give you if you want...
cksup said:
I have 23.21.34 version i can give you if you want...
Click to expand...
Click to collapse
It's simple, you just have to extract the boot.img from any ota zip (suggested the official OTA zip)
Do that and give him then.......it will be very good if he can make the 5.1 stock recovery
cksup said:
Do that and give him then.......it will be very good if he can make the 5.1 stock recovery
Click to expand...
Click to collapse
First of all, you must clarify who is referred to as 'him'?
Secondly, there is no method(according to me) by which you can make a stock recovery from a stock kernel. There are two files namely the boot.img and the recovery.img.
First one is the kernel and the second one is the recovery.
Use the ones you like.
Him meant the op
I don't know if one can make recovery from boot.img.......The op didn't say that either....He said and i quote "I am going to do an experiment to backup stock recovery.img of Lollipop 5.1. To do this, I need stock boot.img(Kernel Version: 3.4.42-gccbac57) of system "
So i thought by using some process he may be able to back up stock recovery....that is why i said like that
and BTW where are those .img files available @Rohitagni
cksup said:
Him meant the op
I don't know if one can make recovery from boot.img.......The op didn't say that either....He said and i quote "I am going to do an experiment to backup stock recovery.img of Lollipop 5.1. To do this, I need stock boot.img(Kernel Version: 3.4.42-gccbac57) of system "
So i thought by using some process he may be able to back up stock recovery....that is why i said like that
and BTW where are those .img files available @Rohitagni
Click to expand...
Click to collapse
U can find them in any zipped firmware files. By zipped firmware files, I mean the zips for stock firmware, or the update zips that many XDA users capture here from their rooted phones to help users who haven't received the OTA, enjoy the new OS, simply by sideloading.
cksup said:
I have 23.21.34 version i can give you if you want...
Click to expand...
Click to collapse
Thanks, but I want 23.26.2 version boot.img.
Rohitagni said:
It's simple, you just have to extract the boot.img from any ota zip (suggested the official OTA zip)
Click to expand...
Click to collapse
I think, we can't extract boot.img from ota zip.
Rohitagni said:
First of all, you must clarify who is referred to as 'him'?
Secondly, there is no method(according to me) by which you can make a stock recovery from a stock kernel. There are two files namely the boot.img and the recovery.img.
First one is the kernel and the second one is the recovery.
Use the ones you like.
Click to expand...
Click to collapse
I'm not making recovery.img from boot.img. I will use boot.img to make my device functional again because I'm going to flash TWRP.img on boot partition and try to root. If device gets root access then I can backup stock recovery.img because stock recovery.img is not over written in process of rooting.
I hope you succeed.........I try to get it from someone
And no @Rohitagni you can't extract boot.img from uploaded update zips but from full firmware zips,yes which is not available
I just saw in general section someone uploaded twrp backup of stock latest 5.1......I can flash that and give the boot.img tomorrow @EthicalHacker
cksup said:
I hope you succeed.........I try to get it from someone
And no @Rohitagni you can't extract boot.img from uploaded update zips but from full firmware zips,yes which is not available
I just saw in general section someone uploaded twrp backup of stock latest 5.1......I can flash that and give the boot.img tomorrow @EthicalHacker
Click to expand...
Click to collapse
I am extremely sorry, for misleading you guys! I just found out that the fsg.bin and the gpt.bin (with logo.bin, etc) are the only things that are available in those zips. So yes, @cksup, you are correct. Please provide him with the kernel, so that miracles can happen
cksup said:
I hope you succeed.........I try to get it from someone
And no @Rohitagni you can't extract boot.img from uploaded update zips but from full firmware zips,yes which is not available
I just saw in general section someone uploaded twrp backup of stock latest 5.1......I can flash that and give the boot.img tomorrow @EthicalHacker
Click to expand...
Click to collapse
That's fine.
I think, the twrp backup; you're talking about is Brazilian. So be careful.
any one found the way to flash twrp on stock 5.1 lollipop previous method don't work.
Ansh2000 said:
any one found the way to flash twrp on stock 5.1 lollipop previous method don't work.
Click to expand...
Click to collapse
Use latest twrp.img and SuperSU zip to root.
And if you have 23.26.2 version then you may help me by posting stock boot.img here.
check out #1st post of this thread.
EthicalHacker said:
Use latest twrp.img and SuperSU zip to root.
And if you have 23.26.2 version then you may help me by posting stock boot.img here.
check out #1st post of this thread.
Click to expand...
Click to collapse
Yes I am on 23.26.2 version but unable to flash. twrp, tried all version of twrp but result is same.
Ansh2000 said:
Yes I am on 23.26.2 version but unable to flash. twrp, tried all version of twrp but result is same.
Click to expand...
Click to collapse
Use twrp 2.8.7 recovery
forum.xda-developers.com/moto-e/orig-development/recovery-twrp-2-8-6-0-touch-recovery-t3100879
with following root guide
forum.xda-developers.com/showthread.php?t=2755336
Ansh2000 said:
Yes I am on 23.26.2 version but unable to flash. twrp, tried all version of twrp but result is same.
Click to expand...
Click to collapse
Hey before you flash TWRP can you do something ....... can you dump for recovery partition and save it in sd card and post it here ....
hey i have a XT1025 on the 5.1 ota update, untouched, and how can i root my device?
cksup said:
Hey before you flash TWRP can you do something ....... can you dump for recovery partition and save it in sd card and post it here ....
Click to expand...
Click to collapse
We can't dump stock recovery without root access and moto e has only one rooting method which is flashing custom recovery on recovery partition. It means we lose stock recovery when we get root access.
That's why I'm taking risk of above mentioned experiment to backup stock recovery.
lnasc256 said:
hey i have a XT1025 on the 5.1 ota update, untouched, and how can i root my device?
Click to expand...
Click to collapse
Check out post no. #16 of this thread.
I have a backup of stock 5.1( 23.26.2) kernel and recovery, I took backup from rashr app after rooting my moto e, and I didnt flash twrp for rooting I boot into twrp, should I upload stock kernel or recovery?
Sent from my Xperia E3 using XDA Free mobile app

TWRP 3.0.2 + Rootkernel + SuperSU 2.79 for 32.3.A.2.33 E5823 - TWRP Restore Data Only

I've put everything into one zip file for the E5823. If you're reading this and don't have the Z5C and you try to get this working... you won't get it working... it'll just close.
This is for the users that are currently having issues with SuperSU + TWRP and Restore functions on Nougat. This works best if you have your Original TA partition saved as a DK.ftf. Disregard this post if you have everything working.
I can't guarantee anything working if you don't have your TA partition backed up, and I'm not going to test it - because I've already lost and had to retrieve my IMEI trying to get this TWRP working.
Use the Stock Sony ROM from 6.0, 6.0.1, 7.0.
When you try to restore - Only Restore the "Data" partition, and you'll only need to Backup the Data partition. I'm still working on TWRP 3.1/Android Bootable Recovery with Rootkernel for Nougat.
https://forum.xda-developers.com/z5...m-fix-twrp-t3560135/post71704926#post71704926
https://forum.xda-developers.com/attachment.php?attachmentid=4099322&d=1491209962
why not just used traditional recovey method since this is to complicate and risky of hard brick
in my experience i couldn't have this rootkernel woking properly ...since the biggining has restore issues flashing issues mount points not mounting properly and worse soft bricks if u dont have recovery on fota kernel.. and if you like to flash aosp base rom you will lose rootkernel recovery so indeed you will still need fota recovery
in fact i have developed i have twrp 3.0 working 100% on fota recovery also planing to update it to 3.2
yes im aware that the tool is good to fix drm and dm
but for flash ,recovery is useless at this point
I only started Android stuff about 4 weeks ago, so I didn't have a build environment ready.
But also this https://twrp.me/devices/sonyxperiaz.html
NeoBeum said:
I only started Android stuff about 4 weeks ago, so I didn't have a build environment ready.
But also this https://twrp.me/devices/sonyxperiaz.html
Click to expand...
Click to collapse
just in time
https://forum.xda-developers.com/crossdevice-dev/sony/patched-magisk-v12-sony-devices-t3582331
way better and even more safe
I wasted my weekend... Fml
altvolt74 said:
just in time
https://forum.xda-developers.com/crossdevice-dev/sony/patched-magisk-v12-sony-devices-t3582331
way better and even more safe
Click to expand...
Click to collapse
I had a quick play with it - but if it's flashed installed in the same way as SuperSU.zip in Recovery- people that are currently having restore errors, will have the same restore errors with MagiskSU.
It did give me a new recovery log to go through. There's some Case sensitive problems too now I think in TWRP.
I have Ubuntu going now too... I had to keep remaking a new virtual drive, because I thought 16GB was enough... then 32... then 64.... so I took it off my scratch SSD and put it on my storage drive as 200GB. The AOSP Sony tutorial said I'd need 100GB.

Can I flash stock miui rom with twrp?

First question is the title basically, wanna flash miui if i happen to not like PE. Can i flash it with twrp?
Second question, If I flash PE without any custom kernels. And flash miui after that. Will i have my original kernel? Or does flashing custom roms change to a custom kernel?
Sorry a bit new to this. Thanks for your time.
1 - Yes, you can flash miui with twrp, just use rom recovery package.
2 - Any rom zip package comes bundled with the kernel. flashing will install the kernel contained in the package.
csleo17 said:
1 - Yes, you can flash miui with twrp, just use rom recovery package.
2 - Any rom zip package comes bundled with the kernel. flashing will install the kernel contained in the package.
Click to expand...
Click to collapse
What is rom recovery package?
thanks for your time man
ParsaMrrelax said:
What is rom recovery package?
thanks for your time man
Click to expand...
Click to collapse
Android devices predominantly followed by following partitions!
/system
/boot
/recovery
/vendor
/storage
/persist
/ta (in xperia)
/overlay (optional)
now RECOVERY (beside parition name) refers to a operating system DESIGNED ONLY to change size of these partitions (ADVANCE) and basic need to spread out(FLASH) operating system according to command by package in certain partitions. -- TWRP is one OUTSTANDING Recovery project over the years. back in old days Philztouch recovery was also popular for Xperia models-
the term "rom recovery package" means, READ ONLY MEMORY ( a android operating system File ) Designed for RECOVERY TO READ and spead the data in /system + / boot & /data partitions for your Poco (or any android based) for boot in to android operating system.
MIUI mainly releases TWO filetypes of SAME ROMS , for example miui10.3.6 has
1. RECOVERY ROM (1.6gb) (to be flashed by TWRP
2. FASTBOOT ROM (2.8gb) which can be flashed by FLASHER running on WINDOWS based System (some times iMac too)
3. Android devices uses many types of processor, SNAPDRAGON processors are famouss (poco uses Snapdragon or SD845) hence Two type of Flashers can be USED to FLASH POCO, 1 MI FLASH (RECOMENDED) (supports Two Mods, on fastboot rom, fastboot & EDL) or QUALCOMS QLOADER flasher (ADVANCE and NOT RECOMENDED)
coming back to twrp,
all custom roms are designed keeping in mind that RECOVERY (such as TWRP) will be FLASHING it on ANDROID DEVICE. so the sequence of flashing such roms are like
1. flashing vendor firmware , from a. vendor firmware , download from https://mirror.akhilnarang.me/MIUI/b...r-firmware.zip
b. flashing pixel experience ROM ( you should also try Crdroid and Havoc)
c. flashing google apps from openapps.org (take arm64>android9.0>MICRO package and hit download) 250+mb filesize
d. (optional) optimus drunk kernel (check development forum for post)
e. flashing magisk18.3.zip (if you want your Device to WAKEUP ROOTED)
now answering you question
1. YES YOU CAN TOGGLE BETWEEN MIUI AND CUSTOM ROMS, but don't make it habit! there is always chance for you to BRICK your device. also you will loose all your data if MIUI uses Encryption method which TWRP cannot READ to operate /data partition. then you must RE FORMATE /data partition via twrp in order to make it accesable for custom rom(s)
2.ANY TIME WHEN TWRP FLASH ANY ROM, MIUI OR ANY CUSTOM ROM, THE OLD KERNEL IS OBSOLETE AND NEW ONE IS PLACED thats why you need to flash magisk everytime you clean flash any rom in order to get root access
please do ask if you need any clarification
might be a old thread.
but i installed a custom rom on my moms phone but i thinking going back to stock. the custom rom is old and has scroll problems...
but i see stable miui has no updates. but can i flash official miui rom from twrp over the custom lingeos rom?
or is it better to update her phone to a more recent custom rom.
either way she will lose her data. plus camera has bugs but i never had the time with work and she working to put it back in a mint working state. cause the scrolling being broking is fuking stupid
tought about miui stable. just to flash it true trwp.
or update it to a more recent custom rom.

TWRP S912 for Android 9 64 BIT

Hello,
I just managed to generate TWRP recovery for S912 Android 9 version, you can install the official TWRP app to flash with in the ROM.
But after reboot the ROM goes back to stock recovery, so for now i am installing everytime i need to use recovery, unless i am able to find a permanent solution.
Link to TWRP
Suggestions welcome if you have for keeping the recovery persistent.
Regards
I was able to keep it persistent but if I go to install all I get for folder names is a mess. Using Superceleron's generic SC normal pie rom. Appeared to install magisk but magisk manager didn't see it and I lost superuser access so I had to reflash rom. I hope you or others can pick up on TWRP for this. Unfortunately I don't have the knowledge so can only test. Liking the Superceleron rom on my T95Z(2/16) much better than poison or stock (so far... still testing...). Glad to see these old devices getting some new love. Hopefully it will continue.
rickpub said:
I was able to keep it persistent but if I go to install all I get for folder names is a mess. Using Superceleron's generic SC normal pie rom. Appeared to install magisk but magisk manager didn't see it and I lost superuser access so I had to reflash rom. I hope you or others can pick up on TWRP for this. Unfortunately I don't have the knowledge so can only test. Liking the Superceleron rom on my T95Z(2/16) much better than poison or stock (so far... still testing...). Glad to see these old devices getting some new love. Hopefully it will continue.
Click to expand...
Click to collapse
Jumbled charcters is because the ROM is encrypted and this recoveery is not able to decrypt it.
Bumping this, going to test this on Aidans rom
Update: could not confirm if it works it looks like the reset button is not mapped on Aidans rom. The weird thing is it works if I use the USB burn tool but not when I do a regular boot.
Doctorbeefy said:
Update: could not confirm if it works it looks like the reset button is not mapped on Aidans rom. The weird thing is it works if I use the USB burn tool but not when I do a regular boot.
Click to expand...
Click to collapse
Do you mean we can flash using amlogic usb burning tool, I am now struggling to install this ROM on khadas 64 android 9 ROM by Highway star
Hi @eagledipesh!
I managed to install your TWRP successfully on Aidan's ROM, thank you very much!
First I unpacked the Aidan' ROM with the Customizatio Tool, then I replaced the original recovery with your TWRP. I repackaged the ROM and flashed it with the AMLogic USB Burning Tool.
With TWRP and I did a full backup and I was also able to restore without errors. However, after restoring and booting the system, it gets stuck on AndroidTV splash screen.
Maybe I need to port the correct TWRP, because when unpacking your recovery with AIK, I saw in one of the files that the model is gxm_q201_2g, but my Android Box is gxm_q200_3g.
1. What base TWRP did you use to create your TWRP?
2. I tried porting TWRP myself from Aidan's ROM recovery, I can even get into recovery, but the letters are all scrambled. Can you help me make my own port?
ulissesemuman said:
Hi @eagledipesh!
I managed to install your TWRP successfully on Aidan's ROM, thank you very much!
First I unpacked the Aidan' ROM with the Customizatio Tool, then I replaced the original recovery with your TWRP. I repackaged the ROM and flashed it with the AMLogic USB Burning Tool.
With TWRP and I did a full backup and I was also able to restore without errors. However, after restoring and booting the system, it gets stuck on AndroidTV splash screen.
Maybe I need to port the correct TWRP, because when unpacking your recovery with AIK, I saw in one of the files that the model is gxm_q201_2g, but my Android Box is gxm_q200_3g.
1. What base TWRP did you use to create your TWRP?
2. I tried porting TWRP myself from Aidan's ROM recovery, I can even get into recovery, but the letters are all scrambled. Can you help me make my own port?
Click to expand...
Click to collapse
I used one of the twrp port guides, twrp was stock one, with stock recovery extracted from initial Android 9 builds by Highway star'
You can use the official twrp as base and then recovery from any of rom for your device
eagledipesh said:
I used one of the twrp port guides, twrp was stock one, with stock recovery extracted from initial Android 9 builds by Highway star'
You can use the official twrp as base and then recovery from any of rom for your device
Click to expand...
Click to collapse
Are you talking about the Wiko Highway Star? Any special reason for using this ROM as a base? How do I know which version of TWRP to use?
i create a twrp for my amlogic T972 but can't boot into it, don't know where to start fix bug
Can you help me build a twrp for this? Or can you teach me do that? Thank you @eagledipesh
Is there now a working TWRP for the Yoka KB2 Pro 3gb on Android 9.0? I would prefer to have an img file, but if there is really no other way, I would also take the zip version.
Thank you and best regards

Categories

Resources