Related
i had just purchased a Verizon galaxy s4 from ebay and found out that its rooted .. Its got the hyperdrive rls10.2 on it and now it says there is a new version 12 I downloaded it . Ive read many threads on here and still cant figure out how to install the new version. Baseband version is vruamdk and the build is vruame7 . can someone point me in the right direction on how to update the new rom .im assuming it has the files on it already to backup etc what I need ... any info would be helpful
thanks
torchdown2011 said:
i had just purchased a Verizon galaxy s4 from ebay and found out that its rooted .. Its got the hyperdrive rls10.2 on it and now it says there is a new version 12 I downloaded it . Ive read many threads on here and still cant figure out how to install the new version. Baseband version is vruamdk and the build is vruame7 . can someone point me in the right direction on how to update the new rom .im assuming it has the files on it already to backup etc what I need ... any info would be helpful
thanks
Click to expand...
Click to collapse
I have deleted my stupidity
DO NOT update to MJ7. You are very lucky to have gotten an MDK phone. Read the Hyperdrive thread, I believe flashing instructions are in the first post. With an MDK phone you'll be able to flash any Verizon S4 ROM, including AOSP builds, if you so choose.
thunderbls said:
You would need to update your build to mj7 the newer version is based on 4.3 not 4.2 http://forum.xda-developers.com/showthread.php?t=2579278 and just to make sure your build is Me7 and the baseband says ...mdk?
---------- Post added at 08:28 AM ---------- Previous post was at 08:22 AM ----------
http://forum.xda-developers.com/showthread.php?t=2565758. For root afterwords
---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------
Lol forget quick post for root... already included in first link... sorry lol
Click to expand...
Click to collapse
yes build is me7 and base is mdk
torchdown2011 said:
yes build is me7 and base is mdk
Click to expand...
Click to collapse
Leave your mdk base alone..you have a diamond. Just educate yourself
Sent from my SCH-I545 using XDA Premium 4 mobile app
spotmark said:
DO NOT update to MJ7. You are very lucky to have gotten an MDK phone. Read the Hyperdrive thread, I believe flashing instructions are in the first post. With an MDK phone you'll be able to flash any S4 ROM, including AOSP builds, if you so choose.
Click to expand...
Click to collapse
is that the first page where says to
1. You MUST READ Through the Entire first page of the Thread
2.You MUST be ROOTED
3. You MUST have a custom recovery installed!
For Verizon Users
FOR MDK Unlocked Phones (TWRP/CWM)
1. Download latest Hyperdrive Rom version
2. Reboot into Recovery
3. Wipe Data/Factory Reset
4. Wipe cache and dalvik cache
5. Install Rom
6. Reboot (First Boot may take up to 10 mins)
7. Let Phone sit for 10 minutes
8. Reboot again
9 Enjoy!
As said DO NOT UPDATE. Read up on loki. Your phone is rare in that it still has the original software on it, its the only one that has an exploit to bypass the bootloader. If you update you could lose custom recovery forever.
thunderbls said:
You would need to update your build to mj7 the newer version is based on 4.3 not 4.2 http://forum.xda-developers.com/showthread.php?t=2579278 and just to make sure your build is Me7 and the baseband says ...mdk?
---------- Post added at 08:28 AM ---------- Previous post was at 08:22 AM ----------
http://forum.xda-developers.com/showthread.php?t=2565758. For root afterwords
---------- Post added at 08:30 AM ---------- Previous post was at 08:28 AM ----------
Lol forget quick post for root... already included in first link... sorry lol
Click to expand...
Click to collapse
Thunderbls, please edit your post, so people don't mess up their phones.
Already done and appropriately annotated as well.
spotmark said:
Thunderbls, please edit your post, so other people don't take your advice.
Click to expand...
Click to collapse
ok I wont update it . as you all can tell just a newbie trying to learn . all your input is thankful..
ive only had the phone for 2 months so real new to me
torchdown2011 said:
ok I wont update it . as you all can tell just a newbie trying to learn . all your input is thankful..
ive only had the phone for 2 months so real new to me
Click to expand...
Click to collapse
Don't rush into anything and take the necessary time.
sent by safestrap
thunderbls said:
I have deleted my stupidity
Click to expand...
Click to collapse
torchdown2011 said:
ok I wont update it . as you all can tell just a newbie trying to learn . all your input is thankful..
ive only had the phone for 2 months so real new to me
Click to expand...
Click to collapse
If your s4 is mdk turn off and boot to recovery by holding volume up and power...if its mdk and running hyperdrive you should already have custom recovery installed...if so you can run pretty much anything available...do some reading and learn up...post your recovery version here...it may not be up to date...older versions work well but don't always play nice with newer ROMs...if you need any help just ask...I myself as well as many others are more than willing to help...if you don't know ask...you don't wanna brick an mdk as chances are you won't find another one
mdk
decaturbob said:
Don't rush into anything and take the necessary time.
sent by safestrap
Click to expand...
Click to collapse
sorry to keep being a bother TWRP/CWM) where would I find this on my phone and I got a private messege saying do this
For Verizon Users
FOR MDK Unlocked Phones (TWRP/CWM)
1. Download latest Hyperdrive Rom version
2. Reboot into Recovery
3. Wipe Data/Factory Reset
4. Wipe cache and dalvik cache
5. Install Rom
6. Reboot (First Boot may take up to 10 mins)
7. Let Phone sit for 10 minutes
8. Reboot again
9 Enjoy!
not sure if this would be the right thing to do any input back would be appreciated
thanks
jamesd1085 said:
If your s4 is mdk turn off and boot to recovery by holding volume up and power...if its mdk and running hyperdrive you should already have custom recovery installed...if so you can run pretty much anything available...do some reading and learn up...post your recovery version here...it may not be up to date...older versions work well but don't always play nice with newer ROMs...if you need any help just ask...I myself as well as many others are more than willing to help...if you don't know ask...you don't wanna brick an mdk as chances are you won't find another one
Click to expand...
Click to collapse
how do I find out what recovery version I have??
torchdown2011 said:
how do I find out what recovery version I have??
Click to expand...
Click to collapse
Install ROM Manager, from the market. When you open it, it will tell you what recovery you're on. Or just boot into recovery.
spotmark said:
Install ROM Manager, from the market. When you open it, it will tell you what recovery you're on. Or just boot into recovery.
Click to expand...
Click to collapse
ok says its clockworkMod recovery 6.0.3.2 and says a newer version of 6.0.4.4 is available
torchdown2011 said:
ok says its clockworkMod recovery 6.0.3.2 and says a newer version of 6.0.4.4 is available
Click to expand...
Click to collapse
Most likely the advanced reboot menu is active. Press and hold the power button. If there is a reboot to recovery, press it. If not, press reboot. If a new menu pops up, press recovery. If not. Power off. Now his the up volume button and press power until it starts up. Then let go of just the power button until some tiny blue writing shows up in the upper left. Then let go of the volume button and wait for the recovery to boot.
Then MAKE A BACKUP. Select that option and do it with the default settings.
Keep your phone plugged in.
Then install the V12 you downloaded. It's aroma so it will step you through.
And keep reading everything you can.
Sent from my SCH-I545 using XDA Premium HD app
brizey said:
Most likely the advanced reboot menu is active. Press and hold the power button. If there is a reboot to recovery, press it. If not, press reboot. If a new menu pops up, press recovery. If not. Power off. Now his the up volume button and press power until it starts up. Then let go of just the power button until some tiny blue writing shows up in the upper left. Then let go of the volume button and wait for the recovery to boot.
Then MAKE A BACKUP. Select that option and do it with the default settings.
Keep your phone plugged in.
Then install the V12 you downloaded. It's aroma so it will step you through.
And keep reading everything you can.
Sent from my SCH-I545 using XDA Premium HD app
Click to expand...
Click to collapse
I get this messege
error while making a backup image of system when trying to do the backup
torchdown2011 said:
I get this messege
error while making a backup image of system when trying to do the backup
Click to expand...
Click to collapse
and now says memory full not able to receive messeges
in dire need of help
Welcome to the MDK master race!
Depending in which recovery you want to use CWM or Team Win. Most likely it has a recovery already installed, go to the power menu and pick recovery mode, you boot to the recovery.
You can update to the latest modem via the modem thread.
Rom build and baseband are different thinks when on the MDK version.
Like someone said here dont upgrade to any other version example MJ7.
The only thinkvyour ever going to need to upgrade to the latest greatest Rom/Android version is your recovery.
Educate yo self!!#
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 03:02 PM ---------- Previous post was at 02:59 PM ----------
Phillz Touch Base is the go to CWM for Verizon imho its in the Development Thread. You can update any recovery by just downloading the zip file and flashing it with the older one.
Sent from my SCH-I545 using xda app-developers app
Hey everyone. How are you guys able to keep root with 5.1? After the update, towelroot didn't stick. Nor could I reinstall it. Supersu doesn't have access either. What do you guys recommend?
You have to re root.
MikeyLee said:
You have to re root.
Click to expand...
Click to collapse
I used towelroot before, but now it says it can't support my device. How did you re-root your device? Did you do it within 5.1? Also, did re-installing TWRP work for you? I lost mine.
This is method I used before. tr.apk
http://forum.xda-developers.com/show...&postcount=376
lowao said:
I used towelroot before, but now it says it can't support my device. How did you re-root your device? Did you do it within 5.1? Also, did re-installing TWRP work for you? I lost mine.
This is method I used before. tr.apk
http://forum.xda-developers.com/show...&postcount=376
Click to expand...
Click to collapse
I think someone said you have to use ADB to flash the new TWRP that is compatible with L on our devices and then flash SuperSU.
I just went back to 2.8.0.0 and it worked for me. Is there a newer version of TWRP?
lowao said:
I just went back to 2.8.0.0 and it worked for me. Is there a newer version of TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=61577016&postcount=303
It pretty easy to get root and TWRP. Here are the instructions, taken from another thread. (Do you guys even read this stuff?)
Credit to Foltz61.
1. Boot to bootloader.
2. Fastboot boot TWRP-L.img
3. Install supersu-2.49.zip (even though I didn't lose root)
4. Reboot back to system.
5. Reboot back to bootloader.
6. fastboot flash recovery TWRP-L.img.
7. fastboot reboot.
8. Boot to recovery and had TWRP
Thanks, I'll try it tomorrow. It's a bit hard to keep track of like 5 threads and 10 new pages in each thread each day.
Does it matter which SuperSU ZIP version we use? Chainfire website shows 2.46.
ScoobSTi said:
Thanks, I'll try it tomorrow. It's a bit hard to keep track of like 5 threads and 10 new pages in each thread each day.
Does it matter which SuperSU ZIP version we use? Chainfire website shows 2.46.
Click to expand...
Click to collapse
kimtyson said:
3. Install supersu-2.49.zip (even though I didn't lose root)
Click to expand...
Click to collapse
I was wondering the same thing. Could someone provide us with a link to a tested supersu-x.xx.zip so we may have it in one thread.
At this time it would be best to not flash twrp. Instead fastboot boot twrp.img then install beta.SuperSU. 2.49
Sent from my MT2L03 using XDA Free mobile app
Lollipop will check the recovery partition and if it isn't stock it will put it back. In order for TWRP to stick you must boot TWRP after you install to allow it to patch the lollipop rom. TWRP must not be read only or else it cannot install supersu nor patch.
You guys got a lot to learn, but this is good, because now maybe some of you will pick up some experience and grow while here on XDA
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
In addition, do not use TWRP from the official twrp website until Dees_Troy gets around to updating his personal device tree since they do not accomondate for the changes seen in Lollipop. You have been officially warned. Unless you like sweats, tears, and heartaches.
lowao said:
Could someone provide us with a link to a tested supersu-x.xx.zip so we may have it in one thread.
Click to expand...
Click to collapse
Here, https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip.
kimtyson said:
Here, https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip.
Click to expand...
Click to collapse
Thanks for the link!
deleted
So my watch recently downloaded the latest 6.0.1 update.zip and I'm more than happy to report: WE CAN FLASH IT VIA TWRP!
This update.zip was grabbed from /cache, however seems to be completely identical with the one you can download from here: https://android.googleapis.com/pack...3ec3e78cb2a7d3.signed-platina-ota-2576000.zip
Exciting news, means we don't have to reset our watch back to stock for it to flash
Here are the download links:
Dropbox
Google Drive
OneDrive
Happy flashing!
loving the new update. its so smooth.
eraycetin said:
loving the new update. its so smooth.
Click to expand...
Click to collapse
That indeed Once the watch was updated it lagged for about 10 minutes still, probably due to it doing stuff in the background after the upgrade. But once that was done it's now working great, smooth and awesomely well!
thanks.
i still wiped out everything to have a more clean experience. and faster.
Yeah I would say the only reason we don't have to go back to stock is that the ota contains completely brand new system image and boot and recovery of course so it thosen't even verify system files as they all get replaced anyway
Can we flash this new stock and then flash a custom kernel? Idk anything sorry, this will be my one annoying question for the day
For 6.0.1 there is no kernel at the moment.
MihaiSG said:
For 6.0.1 there is no kernel at the moment.
Click to expand...
Click to collapse
No kernel for 6.0.1?? Really??
Go here :
http://forum.xda-developers.com/showthread.php?t=3082669
I haven't checked the topic today. Good that it was updated, can't wait to test it. Thanks for the heads up
Gohma Custom Rom
Hey guys,
My watch is currently running Gohma ROM. can i sideload the update and install right on top, or should i return it back to full stock before installing it?
it does have TWRP installed...
livinstyle said:
Hey guys,
My watch is currently running Gohma ROM. can i sideload the update and install right on top, or should i return it back to full stock before installing it?
it does have TWRP installed...
Click to expand...
Click to collapse
you might be able to but doubt it just flash the system image and boot from here
Is it compatible with invisiblek's kernel 6.1?
Edit: this rom is the same as before, MEC23G, theoretically, it should be compatible...
Edit1: It is compatible.
Jhon998 said:
Is it compatible with invisiblek's kernel 6.1?
Edit: this rom is the same as before, MEC23G, theoretically, it should be compatible...
Edit1: It is compatible.
Click to expand...
Click to collapse
Um dude what are you on about there haven't been any updates since. Invisibleks kernel was made for that build anyway you can also try the non stock 6 version on his builds it has smartmax eps instead of on demand
Xmaster24 said:
Um dude what are you on about there haven't been any updates since. Invisibleks kernel was made for that build anyway you can also try the non stock 6 version on his builds it has smartmax eps instead of on demand
Click to expand...
Click to collapse
Lol I was lost I thought that the update was released yesterday, because the xda page of g watch listed this post as 22nd april as for the last activity not the actual post date...
hi guy's.I have a problem with this version.
when I put my phone on silent mode,my watch goes to"don't disturb mode" and when I turn off the "don't disturb mode" in watch,my phone go back to ring mode.I don't like this.
I want put my phone on silent mode and watch doesn't go to don't disturb mode.do you have this problem? Any idea for this?
is there any way to update my lg g watch without using "system update" and without using "stock recovery" ? i have problems with both of them, looking for a third method...
Help
I Download ROM + I Install TWRP On My Watch But I Don't Know to How install with twrp PLEASE Help Me
help
helppp me pls
MehranAB said:
I Download ROM + I Install TWRP On My Watch But I Don't Know to How install with twrp PLEASE Help Me
Click to expand...
Click to collapse
Do you know how to use TWRP? Copy update zip to watch using adb, reboot to recovery then flash zip. As it's a smartwatch you have to touch and swipe screen in a certain way to activate recovery, please search the forum for more info.
lfom said:
Do you know how to use TWRP? Copy update zip to watch using adb, reboot to recovery then flash zip. As it's a smartwatch you have to touch and swipe screen in a certain way to activate recovery, please search the forum for more info.
Click to expand...
Click to collapse
Thank You! But What is the exact command to copy the update file.zip to LG G watch via ADB?
Regards
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
My phone is an Honor View 10 model BKL-L04 (American model) build 8.1.0.133 (C567GT).
These are the steps that I used to remove the stock firmware and recovery and replace them with something more to my taste. I did < 1% of the actual work here, I'm just putting everything that I did in once place so that other people may not have to look so hard to find answers.
Requirements
View 10 - If you don't have one then you're in the wrong place. Do NOT follow these directions for any other phone as both the directions and the links are specific to the model mentioned above.
Cash/PayPal - Most of us don't have the skills to pry out the bootloader unlock code ourselves so we must pay someone who does. God knows the manufacturer isn't going to help us out here
SD Card - You can probably get this done purely on internal storage, but weren't you going to put in a nice, big SD card anyway?
SD Card Writer (optional) - You'll need a way to load files onto the card prior to flashing. IMHO getting an SD card writer is the simplest way, but to each their own.
Unlocking
This guy will get you an unlock code for your View 10 for $22 (USD). Order a Bootloader Unlock Code, select the Huawei option "with IMEI", put BOTH of your IMEI numbers in the comments field, submit it and pay via PayPal. I got a code in about an hour. Once you have the code you can follow these directions to perform the unlocking process. If you need a bit more help getting though it then try this guide.
Flash Recovery
Don't use the official TWRP images. As of Dec 8, 2018 neither 3.2.1-0 nor 3.2.1.-1 worked for me (-0 dropped to fastboot after a few seconds and -1 caused a bootloop when entering recovery). Use the latest unofficial image from this page. Directions included. More detailed directions can be found here but make sure to use the TWRP image from the first link.
Copy Zips
Now pick out a ROM (I went with LineageOS 15.1) and copy all the zips you need to your SD card. The list probably includes the ROM itself, gapps, and some type of su/root package. Put them all on your card.
Flash ROM
If you're going with LIneageOS 15.1 as I did then this guide should get you the rest of the way. It has the links for the ROM itself as well as gapps and the su package. Again, be very careful to match exactly your phone model and architecture (arm64 for the View 10) when grabbing these packages.
Extras
You can find the latest stock firmware image for the BKL-L04 here. Be damn sure your phone matches mine before you use it! If you need to pull out the stock recovery for any reason, you can use the update extractor to do this (grab recovery_ramdisk), then flash it the same way you flash TWRP.
Good luck and have fun! I'll try to help if you get stuck but the real knowledgeable people are those that wrote the articles I've linked to.
Cheers!
- E
Is "twrp_bkl_0.7.img" the latest one?
As of Dec 9 I believe it is, yes.
Eimafn said:
As of Dec 9 I believe it is, yes.
Click to expand...
Click to collapse
It installed but it keeps saying unable to unmount system so I can't backup or flash a new rom.
MikeyJay530 said:
It installed but it keeps saying unable to unmount system so I can't backup or flash a new rom.
Click to expand...
Click to collapse
I didn't have that issue when I was first flashing the ROM, but I do now. If you're having it prior to flashing your ROM would it be because you didn't wipe & format beforehand? The guide I linked in step 5 leads you through this procedure if you need it.
As far as the unmounting error, I think that's something we'll have to live with until the issue is corrected in TWRP.
- E
Eimafn said:
I didn't have that issue when I was first flashing the ROM, but I do now. If you're having it prior to flashing your ROM would it be because you didn't wipe & format beforehand? The guide I linked in step 5 leads you through this procedure if you need it.
As far as the unmounting error, I think that's something we'll have to live with until the issue is corrected in TWRP.
- E
Click to expand...
Click to collapse
Then how can I flash a custom rom?
MikeyJay530 said:
Then how can I flash a custom rom?
Click to expand...
Click to collapse
I think it works if you wipe/format first. The guide I linked walks you through this.
Eimafn said:
I think it works if you wipe/format first. The guide I linked walks you through this.
Click to expand...
Click to collapse
I did wipe/format first lol still messed up
MikeyJay530 said:
I did wipe/format first lol still messed up
Click to expand...
Click to collapse
Hmm. Well, you can either try one of the official builds (here) or wait for the guy doing our customized build to fix this issue. You might even post a note on this thread describing your issue so that he can track how many people are having it.
Sorry I couldn't be more help. The View 10 is not the easiest phone to work with by a long shot.
- E
MikeyJay530 said:
I did wipe/format first lol still messed up
Click to expand...
Click to collapse
You should do it from emui settings not from twrp .
miststudent2011 said:
You should do it from emui settings not from twrp .
Click to expand...
Click to collapse
What do you mean?
MikeyJay530 said:
What do you mean?
Click to expand...
Click to collapse
You have told that you have formatted your device, if you have formatted it from twrp it will cause issues, you should format it from emui system settings.
miststudent2011 said:
You have told that you have formatted your device, if you have formatted it from twrp it will cause issues, you should format it from emui system settings.
Click to expand...
Click to collapse
No I need to do it in TWRP if I want to install a custom rom...lol
MikeyJay530 said:
No I need to do it in TWRP if I want to install a custom rom...lol
Click to expand...
Click to collapse
Seriously you are laughing at me for trying to help you ?
I need to do it in TWRP if I want to install a custom rom --> Where did you get it ?
Currently available TWRP are buggy and are causing issues.
miststudent2011 said:
Seriously you are laughing at me for trying to help you ?
I need to do it in TWRP if I want to install a custom rom --> Where did you get it ?
Currently available TWRP are buggy and are causing issues.
Click to expand...
Click to collapse
Noooo I'm laughing because I'm confused lol I got the twrp from the link on this thread.
MikeyJay530 said:
Noooo I'm laughing because I'm confused lol I got the twrp from the link on this thread.
Click to expand...
Click to collapse
TWRP is not needed if you try to flash openkirin roms they are among the best roms available right now for this device. go to openkirin.net for more details.
miststudent2011 said:
TWRP is not needed if you try to flash openkirin roms they are among the best roms available right now for this device. go to openkirin.net for more details.
Click to expand...
Click to collapse
I'm wanting to flash Pixel Experience though.
---------- Post added at 08:21 AM ---------- Previous post was at 08:06 AM ----------
miststudent2011 said:
TWRP is not needed if you try to flash openkirin roms they are among the best roms available right now for this device. go to openkirin.net for more details.
Click to expand...
Click to collapse
Also, how do I get TWRP off my phone so I have EMUI recovery back?
MikeyJay530 said:
I'm wanting to flash Pixel Experience though.
---------- Post added at 08:21 AM ---------- Previous post was at 08:06 AM ----------
Also, how do I get TWRP off my phone so I have EMUI recovery back?
Click to expand...
Click to collapse
Download full firmware package from firmware finder and extract recovery from update.app and flash it ,
BTW what is your current phone state ?
miststudent2011 said:
Download full firmware package from firmware finder and extract recovery from update.app and flash it ,
BTW what is your current phone state ?
Click to expand...
Click to collapse
Is there a guide for that? Sorry I'm new with this phone. My phone is unlocked.
MikeyJay530 said:
Is there a guide for that? Sorry I'm new with this phone. My phone is unlocked.
Click to expand...
Click to collapse
What is your phone current state, you have just flashed only twrp or any other changes ?
did you format your phone through emui settings before flashing twrp ?
what build are you on currently ?