Hi,
a few weeks ago I got a Samsung X Cover 2 after my loved Defy boke down...Thanks to the rooted image that theboegl created I examined the device and started to port CWM to the device. Some photos of CWM on the S7710 are here. Sorry - cant post outside links before I did 10 posts....attached.:silly: Thanks to OliverG96 who worked on CM for the S3 mini that is quite similiar to the skomer it wasn't a hard job to get it running.
The source is on my github account. (no link - see above - just google: github flxo). Feel free to comment and improve....
Code:
sudo heimdall flash --pit skomer.pit --Kernel2 recovery.img
DISCLAIMER: Use this recovery image at your own risk! You are responsible to any harm that is caused to your device during the use of this software.
Download
Mirror
CWM Changelog:
2013/07/08: Added kernel build with source from Samsung Open Source. Fixed external_sd stuff that enabled restore and backup to the sd.
2013/07/09: Fixed CWM boot loop (reboot recovery menu item or reboot syscall). Updated j4fs and param kernel modules.
2013/07/11: Added ext4 capabilities to installer (needed for otapackage). Updated fstab with reserved area at the partition end.
2013/07/19: Updated to version 6.0.3.3. edit: weird reboot issue.
2013/07/19: Updated to version 6.0.3.6 (cm-10.1). Sideload still not functional.
2013/11/03: Updated to version 6.0.4.4 (cm-10.2).
2013/11/09: Fixed USB and sideload. Do not use.
2013/11/14: Updated to version 6.0.4.5. Added param and j4fs modules to recovery.
2014/01/12: Updated to version 6.0.4.6. <-- USE THIS VERSION
TWRP Changelog:
2013/12/07: Initial TWRP version from Omnirom 4.3 branch
2013/12/21: Source update. Minor kernel fixes.
Thanks for your work!
For those who want to try this beta-build:
download the newest odin-flashable build from here - thanks to @flxo
start Odin >= 3.07
select the downloaded CMW in the PDA section
unselect autoreboot if you would like to test it after flashing immediately
plug your XCover2 in
flash it
let it reboot/if you want to test cwm now:
power off by holding the power button
hold Volume +, Home and Power button simultaneous
you should see cwm
done
BTW: no one should just follow me by doing a reboot recovery, though I have created an odin-flashable restore - build 12.07.2013 for getting out of the "boot to recovery" loop without loosing data.
flxo said:
Hi,
a few weeks ago I got a Samsung X Cover 2 after my loved Defy boke down...
Thanks to the rooted image that theboegl created I examined the device and started to port CWM to the device. Some photos of CWM on the S7710 are here. Sorry - cant post outside links before I did 10 posts....attached.:silly:
Thanks to OliverG96 who worked on CM for the S3 mini that is quite similiar to the skomer it wasn't a hard job to get it running.
The source is on my github account. (no link - see above - just google: github flxo). Feel free to comment and improve....
I did not try yet to flash a zip with the CWM port but so far the graphics look good and the SD is mounted. I attached the recovery image to this post:
Hang on.
cheers,
flxo
sorry for the short description, but it's Friday 9pm and I really shouldn't sit in front of my computer...
Click to expand...
Click to collapse
I'll try this out. Oh and if this works, I'll see if I can start porting any roms to this device now
---------- Post added at 11:28 AM ---------- Previous post was at 10:50 AM ----------
Yo, I made a flashable odin.tar! Enjoy testing guys, cheers
http://rapidshare.com/files/2716144166/recovery.tar.md5
I keep my fingers crossed for it.
It will open new world for our phone.
Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2
TheBoegl said:
BTW: no one should just follow me by doing a reboot recovery, though I have created an odin-flashable restore for getting out of the "boot to recovery" loop without loosing data.
Click to expand...
Click to collapse
Thanks. That fix is exactly what I need right now...
Everyone be carefull - this image is absolutely untested and may brick your device....
Lum_Os said:
I'll try this out. Oh and if this works, I'll see if I can start porting any roms to this device now
---------- Post added at 11:28 AM ---------- Previous post was at 10:50 AM ----------
Yo, I made a flashable odin.tar! Enjoy testing guys, cheers
http://rapidshare.com/files/2716144166/recovery.tar.md5
Click to expand...
Click to collapse
Has anyone tried
kolmanb said:
Has anyone tried
Click to expand...
Click to collapse
Tried flashing, works like a charm. Just hold volume up, home and power, let go of power when you feel vibration and keep hold volume up and home button and you're in cwm! Gonna try port first custom rom, cm10 from s2 and see if it truly works
Hello,
I have just tested : very good ! very good !
Thanks a lot.
:laugh:
Works perfectly super !:laugh::good:
backup: ok
restore: ok
Apology : restore works fine
install zip : from sd card; ext.sd card ok
kolmanb said:
Apology : restore works fine
install zip : from sd card; ext.sd card ok
Click to expand...
Click to collapse
Thanks!
I changed the recovery.fstab to mount the external SD on /sdcard. Storing backups on the real SD is IMHO more convenient.
The updated image is: 20130606_recovery.img
Thanks to TheBoegl for the hint.
flxo said:
I changed the recovery.fstab to mount the external SD on /sdcard. Storing backups on the real SD is IMHO more convenient.
Click to expand...
Click to collapse
Thats great. For everyone who want to flash this with odin try this image - it is the packed version of @flxo.
I have reupped the previous recoveries because they were unflashable with odin.
I really apologize for that mistake my Finnish, Slovenian and Bulgarian members if Odin is stuck, just unplug your phone and select the new image, plug it in again and flash.
This double post is to inform the few of you who have downloaded the file already.
I created an Odin flashable .tar.md5 of the 20130606_1_ version. I tried it myself, works fine.
One nitpicky question: flxo, shouldn't it be 20130706? It's July after all
flxo said:
[*]reboot recovery: reboots device normally. failed.
Click to expand...
Click to collapse
20130606_1_ fixed that for me, the device froze for half a minute and then rebooted into recovery.
EDIT:
Bad news: Somehow, the phone exclusively reboots into recovery now. I don't know if it's due to choosing "reboot recovery" or something else...
HeavyMoertel said:
Bad news: Somehow, the phone exclusively reboots into recovery now. I don't know if it's due to choosing "reboot recovery" or something else...
Click to expand...
Click to collapse
I guess you found my fix for that in the second post :good:
TheBoegl said:
I guess you found my fix for that in the second post :good:
Click to expand...
Click to collapse
Yeah, well, I really shouldn't have followed you on that, I guess.
But many thanks for reminding me of your fix. :highfive:
---------- Post added at 12:45 AM ---------- Previous post was at 12:13 AM ----------
Issue: factory reset formats the whole SD card.
I'm so sorry, can you tell me how to install CWM, I tried to Odin MOD but nothing Nest, thank you very much.
you were faster than i thought.
I've added the description and link in the second post.
Let me know if you need more information.
Related
This is a working build of CWM recovery.
Thank you to those you have confirmed everything working.
credit goes to utkanos he made this.
if you decide to continue building from this, no need to ask, just give utkanos credit
device tree if you want to continue to work from this:
https://github.com/utkanos/android_device_htc_fireball
download link
http://dl.dropbox.com/u/26383143/HTC Incredible 4G/fireball4.img
Has anyone tried this?
droid10 said:
Has anyone tried this?
Click to expand...
Click to collapse
I can try it when I get home (in about an hour and a half)
---------- Post added at 04:18 PM ---------- Previous post was at 04:06 PM ----------
Flashed, works great.
To access the SD card to flash things, rather than choosing "Choose zip from sdcard" you need to choose "choose zip from external sdcard".
This works just like the regular CWM recovery on the Inc2 (For those that had it) no touch screen aspects of this at all.
For reference (and those lazy)
Boot to the bootloader (when phone is off, hold down power button and Volume Down button till you see the bootloader
OR type this in terminal while phone is on and plugged in (with adb and fastboot)
Code:
adb reboot bootloader
once in bootloader, and makesure fireball4.img is in the same folder you are working in
Code:
fastboot flash recovery fireball4.img
Code:
fastboot reboot
- Or choose "reboot" in the bootloader.
And now you have the recovery. To access it (while phone is fully booted):
Code:
adb reboot recovery
It works perfectly. Thanks
this works perfectly. i tried twrp but its not for me im used to ext4 but ive also used cwm in the past with my og inc.thanks for this
---------- Post added at 02:17 PM ---------- Previous post was at 02:06 PM ----------
I'm looking in the download section of Rom manager and I gotta ask is this from the dinc 2
Linch89 said:
this works perfectly. i tried twrp but its not for me im used to ext4 but ive also used cwm in the past with my og inc.thanks for this
---------- Post added at 02:17 PM ---------- Previous post was at 02:06 PM ----------
I'm looking in the download section of Rom manager and I gotta ask is this from the dinc 2
Click to expand...
Click to collapse
im confused by your question?
a recovery is unique to a phone
u can go ahead and try to run an inc2 recovery on your phone and see what happens, but i don't suggest it lol.
i also didn't build this, I asked utkanos and he did it.
I haven't tried/put in any effort to build a recovery.
I'd like to get the soft keys working on this.
andybones said:
im confused by your question?
a recovery is unique to a phone
u can go ahead and try to run an inc2 recovery on your phone and see what happens, but i don't suggest it lol.
i also didn't build this, I asked utkanos and he did it.
I haven't tried/put in any effort to build a recovery.
I'd like to get the soft keys working on this.
Click to expand...
Click to collapse
I'm guessing he means he was using a CWM recovery on his OG Dinc. I also used the CWM recovery on my OG Dinc and was very happy with it on that phone. CWM did all I needed and worked very well with the pro version of ROM Manger to do scheduled Nandroid backups. Based on that experience, I'm leaning towards using CWM, too. (FWIW, I'm also using a CWM build on my Kindle Fire, too)
This is why I asked if he built it from the dinc2 just curious
Linch89 said:
This is why I asked if he built it from the dinc2 just curious
Click to expand...
Click to collapse
sorry I'm still confused
andybones said:
sorry I'm still confused
Click to expand...
Click to collapse
Who's on first?
Jafmf95 said:
Who's on first?
Click to expand...
Click to collapse
Yes
junkmail9 said:
Yes
Click to expand...
Click to collapse
Bacon
Lemon meringue pie.
andybones said:
sorry I'm still confused
Click to expand...
Click to collapse
If you look at his screenshot, you'll notice that ROM Manager thinks his phone is the Inc2. That's why he's asking.
mdmower said:
If you look at his screenshot, you'll notice that ROM Manager thinks his phone is the Inc2. That's why he's asking.
Click to expand...
Click to collapse
Great catch. I missed that entirely. That could create a bit of a problem if he tries to install a ROM. Sounds like a question for Koush.
I checked the download section of Rom manager for ****s and gigs and that's what I found. Secretly, I was hoping that cm would magically be in there
I don't use ROM manager... I manage my own ROMs
andybones said:
I don't use ROM manager... I manage my own ROMs
Click to expand...
Click to collapse
Sure. I never installed any ROMs from it, either, but the automated nandroid back up feature is nice.
Sent from my Fireball using Xparent Blue Tapatalk 2
have you got the device tree that was used to build this?
Lloir said:
have you got the device tree that was used to build this?
Click to expand...
Click to collapse
here is the device tree
https://github.com/utkanos/android_device_htc_fireball
Hello XDA
I'm releasing recoverys since I'm not able to port Cyanogenmod on our phone even if we have all opensource released by LG,
just for the lack of the knowledge, I'm pretty begginer. Hopefully some kind people see this and feel sad about our orphan child L5II and port us CM
This is the second recovery I release for our devices, this seems to be the best in my opinion.
I take no credits for this as I only built it for our device.
So yeah the beautyful PhilZ Touch Recovery is now avaible for our L5IIs.
This is the PhilZ Touch Recovery 6.57.9 Andvanced Edition with CWM v6.0.5.1
We're going to use the same way as for previous recoverys to flash it.
PRE-REQUISITES
1. Root Permissions on your LG L5II
2. Unlocked bootlader
3. Terminal Emulator (can be downloaded from Play Store)
NOTE: I tested this only on E460, I hope this works also on other L5IIs but I'm not sure.
I DO NOT ASSUME ANY RESPONSABILITY FOR BRICKED DEVICES OR ANY OTHER DAMAGE
DURING THIS PROCEDURE, DO THIS ON YOUR OWN RISK.
DOWNLOAD:
(If someone wants to provide any mirror will be appreciated)
http://uppit.com/pbjhcmfju47z/recovery.rar
1. Extract the downloaded file.
MD5 sum:
Code:
[COLOR="red"]BD8BDDD56E50100795F437E7449A20F5[/COLOR]
2.Then place it in your SDcard and open your terminal emulator
and type the following text:
Code:
su
dd if=/mnt/sdcard2/recovery.img of=/dev/recovery
3. When you have successfuly executed the previous commands in terminal emulator reboot in recovery mode to test it
Type this in terminal emulator
Code:
su
reboot recovery
Or switch off your phone and hold VOLUME DOWN + QUICKBUTTON + POWER BUTTON until LG logo shows and then release, it will boot into recovery mode in few seconds.
I really hope it worked for you and you can now enjoy your beautyful recovery.
Let me know about bugs and on which models it works!
Thank you for your attention!
IMPORTANT NOTES:
-As this is based on stock recovery source it seems that LG left us a bug. It won't mount\format sdcard0(internal sdcard). So I've found out that this isn't the fault of revovery in itself but recovery.img containing a bug left by manufactor. So my objective now is to solve it, I can't actually say when it will get fixed, I don't have much time to work on it because of my real life issues.
link is not working
It's working, I just checked it now.
In these days I'll provide some mirrors so there won't be problems.
I can confirm it is working on my e450
it doesn't mount internal storage. not sure if this is because mine is a e450 or if it is the recovery. havent tried flashing any zips yet but will let you know how it goes.
If you send me your stock recovery.img I may build it for e450 and we'll see if that will resolve the issue.
Beershake said:
If you send me your stock recovery.img I may build it for e450 and we'll see if that will resolve the issue.
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/51036208/Android/Stock/mtkdroid/recovery.img
There you go.
You are a legend.
slipsystem said:
https://dl.dropboxusercontent.com/u/51036208/Android/Stock/mtkdroid/recovery.img
There you go.
You are a legend.
Click to expand...
Click to collapse
I will do it today if I have time, if not tomorrow for sure. I'm not a legend, You are a legend because of all development you have done so far this lovely device
EDIT: It seems to be the recovery's in itself issue, I"m encountering this issue even on my E460. I'm trying to figure out what causes it and hopefully resolve.
Just flash slimsystem with no issue s
aroma installer works and it writes to the system partition properly.
very nice recovery
slipsystem said:
Just flash slimsystem with no issue s
aroma installer works and it writes to the system partition properly.
very nice recovery
Click to expand...
Click to collapse
I'm glad you like it, altough credits goes to it's original ideator.
Updated main post with some important notes.
worked on E460 without a problem! Thank you, awesome stuff!
---------- Post added at 01:05 PM ---------- Previous post was at 12:10 PM ----------
Since we have unlocked bootloader and custom recovery, is it possible to custom roms will arrive? Maybe CM or SlimRoms?
0b4 said:
worked on E460 without a problem! Thank you, awesome stuff!
---------- Post added at 01:05 PM ---------- Previous post was at 12:10 PM ----------
Since we have unlocked bootloader and custom recovery, is it possible to custom roms will arrive? Maybe CM or SlimRoms?
Click to expand...
Click to collapse
can you do a backup??
t-driver said:
can you do a backup??
Click to expand...
Click to collapse
I haven't tried it. But I think it should work. I can't try it out because I do not have much free space. (Usually CWM backups are minimum 1 GB)
has anyone done a backup yet? or is there still something missing??
t-driver said:
has anyone done a backup yet? or is there still something missing??
Click to expand...
Click to collapse
I did a back up and restore. Select custom backup and select boot recovery and system
t-driver said:
has anyone done a backup yet? or is there still something missing??
Click to expand...
Click to collapse
slipsystem said:
I did a back up and restore. Select custom backup and select boot recovery and system
Click to expand...
Click to collapse
Full backup is working too, it takes a lot of space if you don't set compression level to high in advanced options. It also may depend on data that you have in your internal sdcard as it backs up that too.
The full backup minimum size for me was 4.9 GB with default compression level(default is set to none).
Instead with maximun compression level(tar+gz enabled, and compression level set to high) the minimum size was less that 2.5GB.
Please note that sizes may be different, it all depens on you. I'd suggest you to do what slipsystem said here. So do a Custom Backup and select following:
Boot(x)
Recocery(x)
System(x)
By doing this way your personal data on internal memory won't be included into backup. This way also the backup max size wont be higher than 1GB(it depends on what did you put system resources, normally its slightly higher than 800MB).
how to check if bootloader is locked or not?
Flash recovery if you get secure boot when trying to enter recovery then the bootloader is locked.
Can you give a mirror? The link dosn't work for me :/
The link also not worked or me please provide a mirror
Introduction
Hello this is my first ROM thought I would share. It is built straight from source. Will be adding cherry-picks along the way. Feel free to ask questions. I will try to answer them. If not will search diligently to help you.
*** Disclaimer
Not responsible if phone blows up etc,ect,ect.
Features
Battery style options
Weather in status bar
Navigation bar height
Search bar in recents
Ad Blocker
Animation options
Gesture Anywhere
App circle bar
LCD Density
Quick setting
Status bar setting
Left handed mode
Power button ends call
Volume button options
Privacy setting
many more!!!
Installation instructions
1. Download ROM
2. Download GAPPS
3. Download SuperSu
4. Boot into recovery
5. Full wipe (Dalvik Cache, Cache, Data, System, Factory Data Reset)
6. Flash Rom
7. Flash Gapps
8. Flash SuperSu
9. Reboot and Enjoy
Upgrade instructions
1. Download ROM
2.Reboot into recovery
3.Dirty flash
4.Reboot and Enjoy
Changelog
3rd post
Downloads
ROM
Gapps
Supersu
FAQ
1.Built straight from source
2. Will try to keep updated
3. Any request send me a PM
4.Hope you enjoy
If you like my work please consider a donation to help buy new computer parts thanks.
Log into paypal and my email address [email protected]
XDA:DevDB Information
AICP-5.0.2-unofficial, ROM for the Google Nexus 5
Contributors
dude1981, scrosler,GROGG88,know.patience,GOOGLE
Source Code: https://github.com/AICP
ROM OS Version: 5.0.x Lollipop
Based On: AICP
Version Information
Status: Beta
Current Beta Version: AICP 5.0.2
Beta Release Date: 2014-12-30
Created 2014-12-30
Last Updated 2015-01-04
reserved
Screenshots
one more
Changelog 2015-1-2
AICP offical changelog
http://mirror2.aicp-rom.com/hammerhead/NIGHTLY/aicp_hammerhead_lollipop-1.0RC0-NIGHTLY-20150102.zip.html
Will add my cherry picks when I put them in.
It's gonna be fun! Thanks
Screen shots? ?
If Someone Helped You Then Just Dont say Thanks...Hit The Thanks Button!
AICP! Do you have screenies?
Prattham said:
Screen shots? ?
If Someone Helped You Then Just Dont say Thanks...Hit The Thanks Button!
Click to expand...
Click to collapse
I have couple:
Sent from my Nexus 5
Do you have a mirror for the download?
Screenshots in second post.:good:
Great! I was looking for it. Where can I see all the features from official aicp?
Sent from my Nexus 5 using Tapatalk
FluffyFox20 said:
Do you have a mirror for the download?
Click to expand...
Click to collapse
Uploading mirror in op now.
dude1981 said:
Uploading mirror in op now.
Click to expand...
Click to collapse
Oh thank you so much c:
FluffyFox20 said:
Oh thank you so much c:
Click to expand...
Click to collapse
Mirror uploaded now.:good:
AvivEliyahu said:
Great! I was looking for it. Where can I see all the features from official aicp?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Look in features in op edited with features.
dude1981 said:
Mirror uploaded now.:good:
Click to expand...
Click to collapse
It still isn't working... ;c Sorry if I am troubling you.
---------- Post added at 09:35 PM ---------- Previous post was at 09:24 PM ----------
There we go! Ingot it.
FluffyFox20 said:
It still isn't working... ;c Sorry if I am troubling you.
---------- Post added at 09:35 PM ---------- Previous post was at 09:24 PM ----------
There we go! Ingot it.
Click to expand...
Click to collapse
So u got it?
dude1981 said:
So u got it?
Click to expand...
Click to collapse
Yes I got it. You have to use Mega ( Beta ) on android.
Now I flashed through Multirom, and when it boots the Boot Logo stays until about 2 min later. Then I reboot, and then when the phone turns back on it skips the MultiRom boot screen and boots right into my Main ROM.
Is this ROM not made for MultuROM?
FluffyFox20 said:
Yes I got it. You have to use Mega ( Beta ) on android.
Now I flashed through Multirom, and when it boots the Boot Logo stays until about 2 min later. Then I reboot, and then when the phone turns back on it skips the MultiRom boot screen and boots right into my Main ROM.
Is this ROM not made for MultuROM?
Click to expand...
Click to collapse
No is not multurom compatible. Will try to make compatible next update
I keep getting "unmount of /system failed; no such volume" when flashing.
I'm running TWRP. First time around, I had wiped Cache, Dalvik, System, and Data, then got stuck at the stock boot animation for 30+ minutes. Since then, I've done a full system format (twice, just to be sure), then wiped everything (again, just to be sure), then rebooted to recovery before using adb push to transfer the .zip files. Still same error, except this time I get the AICP boot animation for a few minutes, then a black screen.
I've been on a bit of a flashing rampage, and a few other ROMs gave me some errors in flashing, but they've all worked after a full system format. Any suggestions? I've searched around a bit, but everything seems vague/unrelated/broken links, and I'm just exhausted.
---------- Post added at 12:39 AM ---------- Previous post was at 12:31 AM ----------
Sorry, I don't know how the thumbs down icon go there, and I can't find any way to edit my post.
athraen said:
I keep getting "unmount of /system failed; no such volume" when flashing.
I'm running TWRP. First time around, I had wiped Cache, Dalvik, System, and Data, then got stuck at the stock boot animation for 30+ minutes. Since then, I've done a full system format (twice, just to be sure), then wiped everything (again, just to be sure), then rebooted to recovery before using adb push to transfer the .zip files. Still same error, except this time I get the AICP boot animation for a few minutes, then a black screen.
I've been on a bit of a flashing rampage, and a few other ROMs gave me some errors in flashing, but they've all worked after a full system format. Any suggestions? I've searched around a bit, but everything seems vague/unrelated/broken links, and I'm just exhausted.
---------- Post added at 12:39 AM ---------- Previous post was at 12:31 AM ----------
Sorry, I don't know how the thumbs down icon go there, and I can't find any way to edit my post.
Click to expand...
Click to collapse
WHAT version of TWRP are you using?
Just got an update on my watch and, as always, pulled the update.zip for you guys!
If you're having troubles installing this ZIP please refer to this post here: http://forum.xda-developers.com/showpost.php?p=67403296&postcount=19
----------
Quick Install "Guide" if it's still failing for you:
1) Install TWRP from THIS THREAD HERE
2) Reboot into fastboot mode by turning the watch off and on again and while the black screen shows up constantly swipe from the left upper corner to the lower right corner.
3) Flash the TWRP provided above and reboot into recovery, then push the unpacked TWRP backup into "/sdcard/TWRP/BACKUPS/xxxxxxxxxxx/" (to get the last folder simply make a backup of only your boot partition first, it's the fastest)
4) Restore the backup provided IN THIS POST HERE onto your watch via the in 1 flashed TWRP
1) MUCH EASIER: Flash these instead the TWRP way, far far easier!
2) Let the OTA update install automatically
----------
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
>> OneDrive <<
EpicLPer said:
Just got an update on my watch and, as always, pulled the update.zip for you guys!
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
Click to expand...
Click to collapse
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
Code:
Unable to statfs '/system/.'.
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
kokesh said:
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
Click to expand...
Click to collapse
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Xmaster24 said:
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Click to expand...
Click to collapse
Thank you. Your recovery mounts /system, but I am still getting the same error.
kokesh said:
Thank you. Your recovery mounts /system, but I am still getting the same error.
Click to expand...
Click to collapse
yeah it can't write to it, you have to use the stock recovery for that. You are able to write to it but you must first format the partition as writable and then flash your system image/ backup. I'm getting the usual "old keys" error of TWRP not error you mentioned, just means The TWRP is too old base
---------- Post added at 11:13 AM ---------- Previous post was at 11:02 AM ----------
Those anyone have a link to the 6.0.1 stock recovery?
Those anyone have a link to the 6.0.1 stock recovery?
Click to expand...
Click to collapse
Isn't it possible to get it from the 6.0.1 OTA?
kokesh said:
Isn't it possible to get it from the 6.0.1 OTA?
Click to expand...
Click to collapse
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Xmaster24 said:
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Click to expand...
Click to collapse
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Xmaster24 said:
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Click to expand...
Click to collapse
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
EpicLPer said:
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
Click to expand...
Click to collapse
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that. I don't think the 6.0.1 source has been released yet so I don't think a recovery could be built with a 6.0.1 base of the lg g watch.
Xmaster24 said:
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that.
Click to expand...
Click to collapse
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
EpicLPer said:
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
Click to expand...
Click to collapse
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
xmaster24 said:
it's not worth it, just flash the stock boot.img once i upload it, waiting for the art cache to build now
Click to expand...
Click to collapse
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Xmaster24 said:
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Click to expand...
Click to collapse
You mean the new OTA kernel or the 6.X kernels?
EpicLPer said:
You mean the new OTA kernel or the 6.X kernels?
Click to expand...
Click to collapse
the stock kernel and nvm it was just AIDA64 glitching out, actually thought more than one core was in use The upside it thought the reboot button is back! don't know why they ever removed it but collio
Xmaster24 said:
nvm it was just AIDA64 glitching out, actually thought more than one core was in use ;-(
Click to expand...
Click to collapse
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
EpicLPer said:
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
Click to expand...
Click to collapse
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Tried, didn't work. My guess is that it didn't handle squash FS. I was left with dead Android guy on the screen
For everyone to enjoy HERE is the stock kernel, @EpicLPer add this to the op to save everyone some trouble. NOTE: you have to boot to system once before the stock recovery is restored. Also it is a twrp backup so you have to adb push it to /sdcard/TWRP/BACKUPS/ to use it. If someone could just get the boot.img raw that would be great, I was too lazy to do it lel.
Xmaster24 said:
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
Click to expand...
Click to collapse
Actually... mine's running pretty well, no lag, no freezing animations, apps take 1 second to open and scrolling is smooth too.
Either I have some leftovers of an old kernel (which I don't think, or, hope) or I'm having a magic LG Watch
with very little activity lately for the LGV20, specifically the H918 T-Mobile variant, I created a TWRP flashable package for the recent H91810q release. this zip flash every partition included in the latest KDZ package with the exception of recovery to keep TWRP. standard disclaimer applies, you do all of this at YOUR OWN risk! because 10q is not rootable, you need to be root'd before flashing this! failure to do so will probably cause you to lose root and/or lose TWRP! and worst of all, because 10q can't be downgraded to 10j (last version where you can still obtain root via dirtycow) because of Anti-RollBack, you're fscked!
NOTE1: you can find the partitions that will be flashed in the updater-script. to be extra cautious you can back up all of the partitions that will be overwritten with the following: dd if=/dev/block/bootdevice/by-name/{partition} of=/external_sd/backup/{partition}.img.
NOTE2: boot partition has been modified only to remove rctd, nothing else so I consider this to still be stock
Instructions:
download H91810u.zip file listed below and put on microSD card
download your choice of root and put on microSD card, choose from either Magisk or SuperSU *Note: v12.0 of Magisk does not work with the LGV20 device in general and v14.0 is recommended.
backup any data from internal "SD card"
boot into TWRP (requires TWRP recovery to already be installed)
create a TWRP backup of the device
flash zip from microSD card by using "Install"
FLASH YOUR CHOICE OF ROOT - Flashing root is VERY IMPORTANT BEFORE REBOOTING!
reboot
profit!
Download:
H91810q.zip
old 10q md5sum: 8c2e76ded9759a63b1ffac86f3941649
new 10q md5sum: c7d4086b3a0a786d1501ef7e4ce22f32 - re-zipped in Linux for proper alignment
H91810r.zip
wrong 10r md5sum: 9e2e1f8c56079d7bf629ce5e375d7551 (this is actually the md5sum for the KDZ)
correct 10r md5sum: 194b2bc41aa6dbdd7b9a371392f7b930
H91810s.zip
10s md5sum: f187fdefe4c3612c5811e9fbeb0748c5
H91810t.zip - rctd and triton both disabled, previous versions only removed rctd
10t md5sum: b00c2f644b15eb15e459c48830caa5da
H91810u.zip - rctd and triton both disabled, previous versions only removed rctd
10u md5sum: f51b2b11a30dc448b0da0edc750bb587
Flashing Process (what flashing this zip does):
flash necessary partition images with the exception of recovery (to keep TWRP) from the KDZ
rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak to prevent stock recovery from being installed on boot
wipes dalvik-cache and cache
BIG thanks to @McNutnut on guidance, as well as his script to put all of this together!
also thanks to @bullghost for the KDZ extractor (https://forum.xda-developers.com/showthread.php?t=2600575)
@Tilde88 for the original updater-script template w/root (https://forum.xda-developers.com/v20/development/us996-nrd90m-modded-notsostock-rom-v5-1-t3526542)
Awesome thanks.. I'm on it!
---------- Post added at 12:50 AM ---------- Previous post was at 12:07 AM ----------
Didn't work... Still shows 10p. I noticed the flash process was rather fast also.
storm68 said:
Awesome thanks.. I'm on it!
---------- Post added at 12:50 AM ---------- Previous post was at 12:07 AM ----------
Didn't work... Still shows 10p. I noticed the flash process was rather fast also.
Click to expand...
Click to collapse
Dude, thanks for whipping this out so fast! (TWSS) I will get right on making a debloated rom from this. Is it ARB 1?
So I HAVE to flash root? Sometimes I don't flash root because of my gear S3 watch.
I just flashed but still showing 10p. But the kernel info shows Sept 12. So the kernel is updated but wondering on why it still shows 10p on software info @ about phone.
storm68 said:
Awesome thanks.. I'm on it!
---------- Post added at 12:50 AM ---------- Previous post was at 12:07 AM ----------
Didn't work... Still shows 10p. I noticed the flash process was rather fast also.
Click to expand...
Click to collapse
hold on, let me re-zip and re-upload. I had used two different methods to add the files to the archive so I'm going to re-do it all with one method
texasaggie1 said:
Dude, thanks for whipping this out so fast! (TWSS) I will get right on making a debloated rom from this. Is it ARB 1?
So I HAVE to flash root? Sometimes I don't flash root because of my gear S3 watch.
Click to expand...
Click to collapse
yes, this is ARB1 and yes, root is needed if you want to stay root'd
As you can see the updater script shows install 10p.
storm68 said:
As you can see the updater script shows install 10p.
Click to expand...
Click to collapse
yep, for some reason using Windows to create zip files causes inconsistencies. I've zipped up everything in Linux this time and double checked the updater script to make sure everything is good to go and am uploading it as I type... I've already updated the OP with the new md5sum and the link should remain the same. I'll give a heads up once it's live
Ok thanks for your time. Appreciate it. ?
storm68 said:
Ok thanks for your time. Appreciate it.
Click to expand...
Click to collapse
done! uploaded and downloaded myself to verify everything is the correct one. this should bring you to 10q for everything... sorry for the troubles of flashing again. don't forget to flash root just in case lol
No problem. No apology needed being you really don't have to do this for the community. Thanks again.
Sorry if I'm asking an obvious question but when did t mobile release a new update? I thought the latest version was 10p???
Flashed... All good!
---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------
Still_living714 said:
Sorry if I'm asking an obvious question but when did t mobile release a new update? I thought the latest version was 10p???
Click to expand...
Click to collapse
Mine came yesterday. Updater to 10q. If you haven't gotten it yet you will..
storm68 said:
Flashed... All good!
---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------
Mine came yesterday. Updater to 10q. If you haven't gotten it yet you will..
Click to expand...
Click to collapse
Any big improvements that you can see?
i flashed and once i unlocked my phone, it kept saying process.android keeps stopping repeatedly. booted back into twrp to restore the backup i made in twrp and now the keeps rebooting to the lg screen. Can anybdoy help me out please. i was ww kernel and 10k
Still_living714 said:
Any big improvements that you can see?
Click to expand...
Click to collapse
I would have to wait and see. But first hand it's about the same as 10p no rctd.
---------- Post added at 04:02 AM ---------- Previous post was at 03:26 AM ----------
Lgv20user said:
i flashed and once i unlocked my phone, it kept saying process.android keeps stopping repeatedly. booted back into twrp to restore the backup i made in twrp and now the keeps rebooting to the lg screen. Can anybdoy help me out please. i was ww kernel and 10k
Click to expand...
Click to collapse
First of be advised that this is anti roll back. Once on it you can't go backwards to other older roms. In reference to your problem you'll have to do a battery pull. Put battery back in. Now hold down volume down and power button at the same time, when you see LG screen release power button for two seconds then push again holding down power. During all this never release volume down. Now you'll get a reset screen with yes and no option. Use volume key to choose yes, twice..... This will get you back to TWRP. In your case I wouldn't even bother with back up but you can try again if want. What I would do is flash something else that I know works. Then decide from there what to do... Maybe redownload again. May be corrupt some how. I assume your on h918. Hope so! Good luck.
storm68 said:
I would have to wait and see. But first hand it's about the same as 10p no rctd.
---------- Post added at 04:02 AM ---------- Previous post was at 03:26 AM ----------
First of be advised that this is anti roll back. Once on it you can't go backwards to other older roms. In reference to your problem you'll have to do a battery pull. Put battery back in. Now hold down volume down and power button at the same time, when you see LG screen release power button for two seconds then push again holding down power. During all this never release volume down. Now you'll get a reset screen with yes and no option. Use volume key to choose yes, twice..... This will get you back to TWRP. In your case I wouldn't even bother with back up but you can try again if want. What I would do is flash something else that I know works. Then decide from there what to do... Maybe redownload again. May be corrupt some how. I assume your on h918. Hope so! Good luck.
Click to expand...
Click to collapse
what do you recommend i flash
Lgv20user said:
what do you recommend i flash
Click to expand...
Click to collapse
Well we really don't know if your system went to 10q now, so........ You can try again. On both, the backup or 10q. Since you know now how to get to TWRP with battery pull you can try both, see what works. Try backup first. If it doesn't work you may have system in 10q now being you backed up a 10k system may not work now. If it doesn't try q again. If that doesn't work then download 10p or redownload 10q and side load on TWRP from computer. Then flash again. These are steps I would do.. if someone tells you different then it's your choice. Different ways for different things.
storm68 said:
Well we really don't know if your system went to 10q now, so........ You can try again. On both, the backup or 10q. Since you know now how to get to TWRP with battery pull you can try both, see what works. Try backup first. If it doesn't work you may have system in 10q now being you backed up a 10k system may not work now. If it doesn't try q again. If that doesn't work then download 10p or redownload 10q and side load on TWRP from computer. Then flash again. These are steps I would do.. if someone tells you different then it's your choice. Different ways for different things.
Click to expand...
Click to collapse
so 10q is showing up. i am having issues with the modem i believe because i dont get tmobile recepetion and as soon as i put into airplane mode, the error message stops.
I haven't tried the 10p weta kernel yet but it may not work being this stock kernel on 10q is updated to the September security patch. May try later today.
First off, thanks for keeping my beloved H918 alive!. Thought all future dev for the V20 was dead.
Now a question. Any timeframe on a debloated version? Not in a hurry mind you, just curious.