Related
I decided to go to Android 5.0.1 from CM10.2 on my Nexus 4. I guess I did not think it though that well and relied on some crappy guides too much.
I have CWM Recovery 6.4.3 installed, so I thought I just place the factory image on the phone and install it via CWM. So:
1) Copied occam-....tgz on the phone;
2) Rebooted into CWM recovery;
3) Did wipe cache/format system/wipe dalvik;
4) Went to install .zip menu... and figured out that the file is no longer on my phone.
I thought OK, I do it via ADB and cable, so installed ADB, drivers etc. and connected my phone to my computer. However, adb does not see it most of the time (when at logo, bootloader, recovery) and only once adb managed to see it (*some number* device unauthorized) while the phone was at Google logo. And I realized I forgot to set up the USB debug option. What are my options now? I can go into CWM recovery, but ADB does not see the device, as I forgot to set up recovery before flashing. Help, please?
The computer sees the phone as MLP, but I still cannot see its storage in Explorer, so I cannot copy the .zip file.
Update
I managed to make adb recognize the phone, but consistently says that it is not authorized, which makes sense. And there is not way I can mount it as an external storage .
first of all, you have a serious lack of knowledge. not activating USB debugging in android settings has no effect whatsoever on ADB usage ability when you are in recovery mode. Secondly, installing factory images is not done through recovery (the downloaded factory image zip is not even flashable so it would work not in recovery), as factory images also contain RADIO and BOOTLOADER images that are flashable through fastboot (not the recovery). The only thing from factory image that you could flash via recovery is a zip file named - in case of 5.0.1 factory image - image-occam-lrx22c.zip (you can find it if you unpack the downloaded factory image on your PC). And this zip file is a classic ROM (system,userdata,boot,cache,recovery partitions). However, even if you were to flash the correct zip (rather than the zip containing entire factory image complete with ROM, RADIO and BOOTLOADER) Android 5.0 (or 5.0.1) comes with updated RADIO (maybe bootloader aswell, i did not check), so you are supposed to update that aswell prior to switching to 5.0/5.0.1
now here is what you should do:
1. download 5.0.1 factory image from gooogle
2. make sure you have ADB and drivers for Nexus4 correctly set up (in order to check wheter it works go see point 3 of this instruction set)
3. boot to fastboot mode (vol down+power) and check if 'fastboot devices' gives you back device id (you should open command prompt in platform-tools folder, where both adb.exe and fastboot.exe are present)
4. proceed with this instruction, start at step 8 http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ (in step 11, name of zip file is the one that is INSIDE downloaded factiory image file (image-occam-lrx22c.zip) and you either do the single zip flash or flashing each of .img files separately (system,boot,userdata,cache,recovery)
ps. 1st android 5.0.1 boot after flashing will take up to 15 minutes. (it took 10 in my case)
Update 2
Thanks dzumagos! Sure, I do not claim to be a specialist by any means. I managed to successfully install Cyanogenmod many times, so thought I would give this one a go as well.
I read your post after I fixed the issue. Basically I did exactly what you suggested, but following another guide and it worked fine, also took it around 15 minutes to load the first time. I noticed I do miss a few tricks from Cyanogenmod
Hello. Sorry for my english. I want flash my phone via rootjoy to Arcatarc's MIUmIZERO and i only can see miui logo. next i want back to stock rom from needrom via sp flash tool, i followed instructions and i stop, when red status back not change for 20 minutes. and i can't charge my phone, can't conected to pc, can't turn on, looks like dead. How unbrick my phone? please help
problem solved
how did you solve it? please let me know as i am in the same boat
If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.
it is dead . the phone wont turn on . the pc wont recognise it anymore , it was fine ... untill i tried to flash stock through sp flash tool .
i was running antarcts emui,.... tried flashing using the method on umi digi forum : http://umidigi.com/forums/topic/how-to-restore-rom-version-3-03-2/ ... preloader was unticked, and when i tried firmware uopgrade option...nothing happened, and the phone was dead after that.
thepopos said:
If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.
Click to expand...
Click to collapse
I managed to make it boot.
The problem is I have twrp and some chinese recovery . And I cant go back to stock.
Fastboot cant flash recovery for some reason ... so I can go back to rootjoy.
use adb side load an try to flash a working rom, the original one from umi website or emui.
can you get in recovery mode? volume (+ or - try both) and power button for some seconds
if yes go adb side load, (check google) and transfer an original rom, then flash it again in the recovery
My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?
Pospa420 said:
My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?
Click to expand...
Click to collapse
If the system is unstable with popups etc or with damaged partitions you can get past that with TWRP.
Boot into recovery Wipe/Advanced Wipe. Then after that is completed, without rebooting, Format Data. That should sort out your partitions.
Then Install ROM from the recovery. It will need to be on the device. If your new ROM is not already there plug in a USB lead and transfer the zip file from your pc.
If you want to re-install your backup, do that instead.
If that doesn't work Backup in TWRP, even though there is no system. Then copy your Nandroid backup (must have been made via TWRP) and paste into the same folder as the Backup you just made, overwriting if asked.
I have had to do all this myself!
Good luck
Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.
It looks like memory become write-protected...
YrP said:
Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.
Click to expand...
Click to collapse
Hi
Did you Advance Wipe and Format Data?
I found that worked.
Alternatively, you could use Rootjoy to put just about any ROM on. CM 12.1 works ok.
Once you have a stable installation, install a custom recovery like TWRP 2.8.7 from Needrom. I used Mobileuncle, an app from the Playstore. However, I looked just now and it doesn't seem to be available.
I have tried Rashr, but couldn't get it to work.
Once you have it all stable you can flash the ROM you really want via TWRP.
Good luck
Advance Wipe and Format Data or flashing new stable ROM via TWRP did not work for me. The same result- unable to mount /system.
Rootjoy and Mobileuncle could be used if phone is working. My phone works in recovery mode only.
I tried to flash different recoveries but did not find the way to do this. As I wrote, Sp Flash Tool, Fastboot and Adb Sideload did not make any changes to my recovery. I think, flash new recovery will help if I found the way)
Or if I discover the method to test and\or repair /system partition from PC
But thank you for answer)
@YrP
Rootjoy works from your pc
Yes, Rootjoy- works)
But for establish connection phone must work too.
And not in recovery mode.
@YrP
I have already done all this with my daughter's Zero.
However, it's in bits at the moment while we wait for a part from China. So I can't go through the process with you live, step by step.
I am in the UK.
If you send the phone to me I will try and fix it for you.
PM me if you want to go ahead and I will let you have my address.
I am in Ukraine, it is too far from UK)
I will keep trying to find the way to fix it by myself.
But thank you very much for your attention and advices.
@YrP
I have got my daughter's phone back together and fixed (mostly).
Did you manage to get your Zero going?
Sent from my Nexus 4 using XDA-Developers mobile app
@goldbear
My UMI is still bricked(
It is flash memory problem, I think.
I am trying to find the tool to remap internal memory, to move SYSTEM part to other physical place. But did not find it yet.
What was your way?
Zero stutters, processes crash or the phone will not boot into System
Have you already tried a Factory Reset or re-installed the ROM?
What can you do?
You could try the following. However, if your phone blows up, orders a takeaway or elopes with your girl-friend, please don’t blame me.
1. Provided you already have TWRP custom recovery installed and your phone is powered down boot into Recovery: hold the volume down and power buttons until the Zero logo appears then let go
2. Select Wipe/Advanced and select Dalvik Cache, System, Cache and Data. Slide to execute
3. Select Format Data/ type yes and slide to execute
4. Reboot into Recovery without installing a new ROM
5. Select Backup, choose SD card rather than internal storage and give the file a memorable title like Blank Backup and date. Select Boot, Logo, Recovery and Uboot. Slide to execute
6. The next step requires you to have a Nandroid backup made via TWRP already made of a stable ROM. If it isn’t stable or you don’t have one I have attached a clean backup below. It’s derived from Cyanogen Mod 12.1. This is based on Lollipop 5.1, with Gapps and rooted. I have found this to work. As the title of the file suggests, it’s a factory reset, ie no personal data included. Download it to your pc unzip and save it.
7. Connect your phone to your pc via USB cable and open Windows Explorer
8. Find your stable backup or the one below and drill down until you see the folder with 15 files, starting with data.info and ending with uboot.emmc.win. Select all and Copy.
9. Open another window and find the TWRP folder on the SC card of your phone. Drill down to the same folder containing similar files as to step 8 above. Click in folder and Paste. When prompted select Copy and Replace, all and Ok
10. If your pc doesn’t show your phone and the SD card, in recovery select Mount and USB storage.
11. In Recovery select Restore and the Blank Backup (or whatever file name you gave it, now populated with usable ‘data’). Slide to execute
12. Give it time to load and boot up
13. You should be good to go!
If you don’t like CM 12.1 installing a new Launcher from the Playstore, like Cheetah will make it run smoother. Everything after that is down to you.
Of course, you could flash another ROM via TWRP
The backup below was made via TWRP 2.8.6. This is also attached below. You can install this via a previous version of TWRP as an image. Unzip it first.
Assuming this doesn’t wreck your phone and you like the guide please click Thanks below.
https://drive.google.com/file/d/0ByoLjFrSKxLwc01UUWZBZEQtbWs/view?usp=sharing
https://drive.google.com/file/d/0ByoLjFrSKxLweGhqNGJuVGV1a0U/view?usp=sharing
My phone, the LeEco Le Pro 3 LEX727 ZL1_NA US model is on the latest EUI 5.8.021S. I am able to open the adb tools in command prompt and get my computer to recognize my phone with "adb devices", but when I go to the stock fastboot with the Chinese and English writing and use "fastboot devices" nothing shows up. I'm using the latest adb tools and am clueless as to what to do.
Unlock Bootloader - Le Eco Pro 3
If you are not seeing your phone ID in ADB
Did you enable enable Developer options, or chosen MTP?
Its possible that the Android driver driver is outdated, or just try another usb port, preferably in the back of the machine.
Go here to check a whole list of possible causes: https://appuals.com/android-phone-not-showing-up-on-pc/
More than you asked for:
Since you seem to be new to your Leeco phone and new to using custom roms, I am going to go ahead and answer your current question and provide you steps needed to move forward. No big deal, I just copy pasted my notes ( with a few edits)
First steps that you need to take:
1. You will first need to unlock the bootloader :
PHP:
https://forum.xda-developers.com/showpost.php?p=71566961&postcount=203
2. Install Twrp :
PHP:
https://twrp.me/leeco/leecolepro3.html
****** Scroll down to see: Fastboot Install Method (
3. Right now just use ADB. But for the future, I highly recommend that you buy an OTG drive: it makes the whole process a thousand times easier: They are cheap somewhere near $5 and worth ten times that
Unlocking the Bootloader
You can save your self alot of time by looking up how to give ADB system wide privileges: this will allow you to flash files without tying the directory path.
Mauronofrio created a tool called: "TOOL ALL IN ONE"" it's great, install it and check for updates.
PHP:
https://toolaio.tk
The all is one tool is excellent and you can use it to install everything if wanted.
I usually recommend it for novices that can use it to help with unlocking the bootloader and installing TWRP.
The tool will also update your copy of ADB, android Drivers and provide system wide privileges for ADB
LETS RECAP : Choose using the All in One Tool or the ADB Method
**********BEFORE DOING ANYTHING*******************
Make sure you have enabled the developer tools,
Turned on USB debugging
Authorized your computer on your device I.E: “MTP”
Make sure the All in One Tool can see your device
(*) Select your device from the drop down menu, then click check
(*) Choose to install drivers, and set ADB and fastboot privileges from advanced menu.
(*) First attempt to unlock, then check bootloader status
If you have a X727 you will need to flash : emmc_appsboot.mbn from this zip :
PHP:
https://androidfilehost.com/?fid=313042859668275431
Next, choose Recovery flasher and manually select your copy of TWRP
After you have received the success message, I recommend doing the rest of the install manually within Twrp Recovery.
(*) Reboot into TWRP and begin installation of your Rom, Gapps and Magisk.
Using the ADB Method
Install ADB/Fastboot tools on your computer
PHP:
https://wiki.lineageos.org/adb_fastboot_guide.html
1. Make sure you have enabled the developer tools,
2. Turned on USB debugging, and authorized your computer on your device “MTP”
3. Enter fastboot mode on phone (hold power and VOL -)
4. Make sure adb can see your device when you run "adb devices"
5. type: fastboot devices
6. fastboot flash aboot emmc_appsboot.mbn
7. Run { adb reboot bootloader } - No spaces (before/after)
8. Run { fastboot devices } to make sure you see your device
9. Run { fastboot oem unlock-go } to unlock your device temporarily
10. Run { fastboot oem device-info } to verify unlock status
11. Run { fastboot boot recovery_twrp-3.2.1-0-zl1.img }
12. 5. Reboot back to TWRP and begin installation of your Rom, Gapps and Magisk.
13. 6. If you wiped data, your device will now proceed to re-initialize itself as if from the factory
Concerning your device's storage,
When you boot into twrp you will see a message that states that the storage is encrypted.
*****************Important************************ ******************
Ensure that you have TWRP installed as the primary recovery
Ensure that you have TWRP installed as the primary recovery
Ensure that you have TWRP installed as the primary recovery
Ensure that you have TWRP installed as the primary recovery
To remove encryption you will need to format the storage
(Anyone who says otherwise has the X720 and not the X727)
You could also try to skip the formatting step. But you will very likely have permissions issues and get errors and you will eventually have to come back and format ( Again as long as Twrp recovery is install there is very slim chance of ever bricking your phone.
To format the storage
Go to Wipe, choose Format Data and follow the instructions.
This will erase all of photos , music, etc
If you wiped your data partition, you'll need to push the zip file to the newly formatted storage. - This is one BIG reason why using OTG is better. You can use Mauronofrio's "TOOL ALL IN ONE"" for pushing the ROM, Gapps, and Magisk to storage.
Root: You absolutely should root!
NOTE: If you have unlocked the bootloader and flashed TWRP to the recovery partition. But have not yet flashed a Custom Rom the OS will likely reset back to the factory recovery UNLESS YOU ROOT THE SYSTEM. Your device is still unlocked. But the recovery can be overwritten by the stock EUI system, so beware.
Installation of Rom, Gapps, Magisk
Boot into TWRP recovery
1. Go to "Wipe" and then to "Advanced Wipe".
2. Mark "Dalvik / ART Cache", "System", "Data" and "Cache".
3. "Swipe to Wipe" and proceed back the main menu.
4. Go to "Install".
5. Select the ROM zip file and then press "Add more Zips" and select the Gapps zip file, and then the Magisk file.
6. "Swipe to confirm Flash" and wait for some time.
7. After the flashing is finished, just reboot to system.
Finished!
If you need help or have a question message me, I would much rather help you with a successful install versus helping you unbrick your phone.
Thank you for your reply. I figured out the issue. Windows 10 updater wasn't auto installing the driver for some reason even though I have auto update ticked.
simpbrackets said:
Thank you for your reply. I figured out the issue. Windows 10 updater wasn't auto installing the driver for some reason even though I have auto update ticked.
Click to expand...
Click to collapse
You have manually install those drivers usually.
Sent from my LEX720 using xda premium
I have the same issue in Windows 10. All In One Tool sees my x720 in adb mode, but when I switch to bootloader, the phone is gone. Device manager then shows unrecognized android device. I have LTSB version of Windows, so maybe that's why it won't auto install the needed driver. Could anyone point out what kind of driver exactly do I need, so that I can install it manually?
Problems with rooting, loading ROM then recovery & download images -some solutions
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810p rom (H91810p_00_0717.kdz) downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB Sideload
Download Magisk-v16.0.zip and copy to adb directory.
On Windows PC connect Cell with USB and in CMD window type (copy/paste):
adb start-server
adb sideload "Magisk-v16.0.zip"And never update migisk after installing from above or will lose root. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
4. No need to download UPPERCUT (that is hard to download), because LGUP works fine without UPPERCUT.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin
shahinman said:
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810P that needs to be reloaded was missing in original links - I think I downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB Sideload
Download Magisk-v16.0.zip and copy to adb directory.
On Windows PC connect Cell with USB and in CMD window type (copy/paste):
adb start-server
adb sideload "Magisk-v16.0.zip"
And never update migisk after installing. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin
Click to expand...
Click to collapse
You can restore download mode by flashing the zip in the original lafexploit thread, but make sure you have twrp on the recovery partition. Make sure you are on the latest version of twrp, when you flashed twrp, you were supposed to format the data partition before flashing the rom.
Sent from my LG-H910 using XDA Labs
For access to Data in TWRP: In the original thread there is nothing about formatting, but in step by step guide there is and I followed - however it does not specify what partition to format. I also ran ./step2.sh script per instructions.
Anyhow as I mentioned above I rebuilt and reformatted the Data partition and that did not give me access. I am on the TWRP 3.2.1-3. What partitions do I need to reformat anyhow?
To flash recovery: I used TWRP and flashify to flash recovery-twrp-h918-2018-10-18.img and it flashes but does not work - I get to fastboot with Vol- & USB.
shahinman said:
Problems with rooting, loading ROM then recovery & download images -some solutions
I started with stock LG v20 T-Mobile H91810P and followed this step by step & the original threads. I loaded the latest stock Oreo from H91820H from here instead of latest Nougat H91810U - Pie & some other versions had too many things not working.
In the process there were a few problems -the major ones are following with solutions, some from here:
1) The file H91810p rom (H91810p_00_0717.kdz) downloaded from here.
2) I lost root several times, but had TWRP. So I used adb sideload like:
Boot/start TWRP and the start ADB SideloadDownload Magisk-v16.0.zip and copy to adb directory.On Windows PC connect Cell with USB and in CMD window type (copy/paste):adb start-serveradb sideload "Magisk-v16.0.zip"
And never update migisk after installing from above or will lose root. Also no need for SU.
3. Camera did not work and people could not hear me nor could I hear them when I picked up a call - A reboot/restart fixed it.
4. No need to download UPPERCUT (that is hard to download), because LGUP works fine without UPPERCUT.
I have 4 problems remaining -any help for solutions here is appreciated - especially exact type help please:
1) On LAF/Boot (original download) partition: Vol+ & connect to USB caused the download mode to come on for about 2 seconds and then TWRP (however I am glad that TWRP is here) -Prefer this to be the original download mode.
2) On Recovery patition: Vol- & connect to USB causes fastboot to come up. Flashed the recovery-twrp-h918-2018-10-18.img (renamed to recovery.img) to recovery partition using flashify and TWRP unsuccessfully. -Prefer this to be TWRP.
3) TWRP cannot access the Data partition. Rebuilt and reformatted Data from TWRP without success. -Prefer access to Data from TWRP.
4) At boot time: I like to get rid of the warning that my bootloader is unlocked. -I can live with this one.
After thoughts: Now that I am rooted on the latest stock Oreo H91820H -I am not sure what I want to load that I could not before?! overclocking the CPU or changing the hue on the display is not a big deal for me at all. & Yes I will uninstall some bloatware - but that is not so bad on this phone anyhow. Any good ideas or a better/later rom than H91820H that has all things working, do please let me know. I am glad that I rooted, ahh the challenge, but if I have no other reason such as to load a program then I think I will revert back to stock and unlock the bootloader & let the ROM updates come from T-Mobile & LG.
-Shahin
Click to expand...
Click to collapse
I had this same situation and ended up bricking the phone, can't get into recovery, stuck in boot loop. This was months ago, just got another v20 and ready to try again. Previously I'd successfully done 3 v20's.
Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).
Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate
unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself