There are threads about saying I can use HiSuite to backup a 6P. But cannot find any info that it is 100% compatible with 6P.
I have tried with adb drivers and Huawei drivers that I think came with HiSuite and tried HDB drivers.
Windows10 can see my phone and I can browse the memory card.
I can use Mobikin to see my sms and other stuff but I don't want to purchase the software if HiSuite is supposed to work.
I need to backup the entire phone as my battery only lasts 5 hours or so and VodafoneAU say there is warranty on the phone and can get it fixed but data will be erased in the process.
I have Android SDK installed and still NG. I have USB debugging on but there is no way to download HDB on the phone as is shown on other Huawei models .
Any ideas as I have been looking for 4 hours to resolve and I am over it!!
HiSuite is compatible w/ the 6P, but the Huawei Backup app (required to be used in conjunction w/ HiSuite) in the Play Store is not.
Hisuite used to work fine on Marshmallow roms but after Nougat the Hisuite.apk that is responsible for synchronization between N6p and PC stopped being able to be installed to the phone from the moment the phone is connected to PC. I think Huawei abandoned the apk development for N6p after Nougat introduction.
Related
1. Install LG PC suite:
http://www.lg.com/uk/support/pc-suite
2. Connect the phone and suite will install update to support it.
3. Choose "Mobile device"->"Mobile device software upgrade"
PC suite will start download, then restart the phone and upgrade it to the last official version.
Then restore the root with Purple drake lite and you are good to go.
PC Suite gave me a lot of problems. It initially worked on my windows machine, but a reformat of that one and I can't install PC Suite on it anymore. Keeps giving me an NSIS error. PC Suite installed fine on my Macbooks but it won't detect the phone. grr
what worked for me was downloading the drivers and the LG Mobile Support Tool (do a search)
this won't let you sync stuff, but it will let you update your phone to the latest available software. For me, it turned out to be version g.
Purple drake root worked after this, and all software and most settings unchanged. Had to turn on xposed again though, and experimental settings with greenify to get everything just like it was before the upgrade.
Hi all,
I enrolled into the Android Beta program when 7.0 stable was released so that I would receive the OTA earlier and as soon as I received it I un-enrolled. Since then I have not been receiving OTAs and my Security Patch level is August 2016. Checking for updates says my device is up to date. I decided to side load the 7.1.1 OTA to my device so that I would have the latest Android version and security patch and hopefully this would fix my OTA issue too.
I'm running macOS 10.12.1 and I downloaded the OTA file from Google's site and installed ADB for Mac using a Terminal command from xda. My phone is recognised in Terminal if I run adb devices when it is fully booted and in Photo Transfer mode, but when I put my phone in Recovery mode and select install from ADB and then run the command again my phone is no longer recognised. I try running adb sideload <OTA Filename.zip> but I get error: no devices found. USB debugging is enabled and my cable is high quality and supports data transfer, so it's neither of those things.
I don't want to do a factory reset because I don't want to lose my data, and I have wiped the partition cache too which also hasn't worked. I've looked for a long time but can't seem to find a solution but figured some clever being on here might be able to help me. Any suggestions?
nathanmiah said:
Hi all,
I enrolled into the Android Beta program when 7.0 stable was released so that I would receive the OTA earlier and as soon as I received it I un-enrolled. Since then I have not been receiving OTAs and my Security Patch level is August 2016. Checking for updates says my device is up to date. I decided to side load the 7.1.1 OTA to my device so that I would have the latest Android version and security patch and hopefully this would fix my OTA issue too.
I'm running macOS 10.12.1 and I downloaded the OTA file from Google's site and installed ADB for Mac using a Terminal command from xda. My phone is recognised in Terminal if I run adb devices when it is fully booted and in Photo Transfer mode, but when I put my phone in Recovery mode and select install from ADB and then run the command again my phone is no longer recognised. I try running adb sideload <OTA Filename.zip> but I get error: no devices found. USB debugging is enabled and my cable is high quality and supports data transfer, so it's neither of those things.
I don't want to do a factory reset because I don't want to lose my data, and I have wiped the partition cache too which also hasn't worked. I've looked for a long time but can't seem to find a solution but figured some clever being on here might be able to help me. Any suggestions?
Click to expand...
Click to collapse
I'm going to assume you are completely stock with no root or custom recovery. Have you tried re-enrolling in the Beta and rebooting? You may get a new OTA after enrolling. Sounds like you may also not have the correct drivers installed to properly use the LATEST version of ADB/Fastboot. Sorry I can't help you with a Mac, but there are also several toolkits for PC that automate this for you. NRT by Wugfresh, and Skipsoft to name two.
v12xke said:
I'm going to assume you are completely stock with no root or custom recovery. Have you tried re-enrolling in the Beta and rebooting? You may get a new OTA after enrolling. Sounds like you may also not have the correct drivers installed to properly use the LATEST version of ADB/Fastboot. Sorry I can't help you with a Mac, but there are also several toolkits for PC that automate this for you. NRT by Wugfresh, and Skipsoft to name two.
Click to expand...
Click to collapse
I contacted Google and they said the only solution was to perform a factory reset. I didn't want to do that so I just enrolled into the beta again, received the 7.1.1 update and then un-enrolled. Not sure if I'll have the same problem going forward but if I do then I guess I'll have to do a factory reset
Thanks for your help!
Hello, short Story before. I got a full Hand of non working mobile phones because being full of a hell of viruses.
5pcs. younger ones.
2 Huaweis and 3 Samsungs.
Well so far 4 PCs. are saved.
Getting into the phone wasn´t possible anymore. Data not important so I resettet over the Buttons to original Status. -> Worked fine.
But one Piece which is a Huawei P9 Lite guess it is a single sim? was the button method not possible cause it wanted a Software update and Installation of WLAN failed (EMUI)
Getting into the phone for any informations was also not possible because of all the viruses and not working right ahead anymore.
Well ok -> will use High Suite for stock Firmware -> this mobile phone is not supported and also couldn´t activate MTP as I am not in the phone. So far.
Next Idea -> ok. will take the C900B300 and go back to Marshmallow. From original HUAWEI site.
Took the European Version in German. Did it over EMUI (hold 3 Buttons) and worked so far but when I turned on I was stucking on the WIFI+. Even pressing the button -> further nothing anymore. So I thought -> maybe another stockfirmware useful.
Again C900B300 and then I think I did the big mistake. Took out the sdcard during it was rebooting (HUAWEI was already visible) and now it is big crap. Stucks at HUAWEI. Turning off not possible. This EMUI is not possible anymore. Just with a trick I am able to get into fastboot. Yeah. But what then? Reading TRWP which I know from Samsungs but putting it on with ODIN. ODIN doesn´t work with Huawei. Do I Need TRWP to get it back to normal Firmware? Mobile phone was never customized or anyhting else. just normal stock was on it and is the wish to get a clean back. Resetting to factory was not possible anymore.
So my questions, even I know it is my fault. Any rescue possible?
What could be the best stock Firmware. I Guess it is a single sim from Austria unlocked and unbranded. Would also take Nougat again. Just wanted to get it back to normal working and now I guess I have a big letter holder. Model from the backside is VNS-L31. More I don´t have.
Thanks a lot for any help for my being an idiot. Samsungs are much more easier than HUAWEIs.
Blimey mate,
This really just boil down to what partitions were damaged in your case- Most likely your system and data,
however since you are still Technically running unmodified emui you could manage to sort of salvage it.
The logic is this:
Most custom roms for the p9 lite build on top of emui (patching the system image) rather than replacing it (like the way samsung smartphones do)- so you could flash the rom, it would wipe your phone clean of viruses in the process and then proceed to do a hard restore back to emui.
1.) get your phone into fastboot and flash this twrp http://www.meticulus.co.vu/p/forum.html#nabble-td27
2.) Then flash this rom : http://www.meticulus.co.vu/p/ressurection-remix-for-hi6250-devices.html MAKE SURE YOU FOLLOW THE INSTRUCTIONS ON THIS SITE VERY CAREFULLY
3.)Follow this guide to do a hard restore https://forum.xda-developers.com/huawei-p9lite/how-to/tips-revert-custom-rom-to-official-t3668413
good luck!!! if you have any questions hit me up!
Hi
Hi Exiatron00,
thanks a lot for your maybe solution way. Will do it this evening after work and come back.
Hopefully it works cause as mentioned in other threads -> don´t think that the original owner opened the Debugging so that I can work over a tool. FRP locked is in fastboot. This was already mentioned in other posts which I have read here in the forums.
Thanks for your step by step explanation. Will do it. Hopefully it works. I am really pissed of my own that i was unpatient with the sdcard. That´s a mistake which shouldn´t happen. Anyway it did. So i will try to do everything to get back working again. I am from IT so I am not such a DAU but newbie with HUAWEIs. Most are Samsungs.
Will give Feedback.
CU
If u need to transfer files , just boot into twrp (it has built in mtp support) , then transfer the file from ur PC to phone via a micro us b cable.
If you are unable to fix the phone I do actually have a FULL twrp backup of my phone (EMUI 5- single sim Europe VNS- L31 C432B370) hit me up if u want it.
Hi,
well adb for flashing not working as device not found. Hi Suite installed. Guess that the USB Debugging is not enabled. hrmpf.
There is a similar thread of somebody with no enabled USB Debugging.
https://forum.xda-developers.com/nexus-4/help/fastboot-recovery-remotely-enable-usb-t2177440
He writes an solution how to enable in fast boot mode with using N4 toolkit.
Search for a p9 lite toolkit and found this
https://forum.xda-developers.com/hu...nt/europe-vns-l31-toolkit-bootloader-t3432873
may could work?
Big **** -> as Long as USB Debugging is not enabled as Long I am not able to Flash TWRP over adb.
If I connect to PC Hi Suite opens automatically. So driver should be fine as pc recognize the phone.
hm?
Got it working somehow
Exiatron00 said:
If u need to transfer files , just boot into twrp (it has built in mtp support) , then transfer the file from ur PC to phone via a micro us b cable.
If you are unable to fix the phone I do actually have a FULL twrp backup of my phone (EMUI 5- single sim Europe VNS- L31 C432B370) hit me up if u want it.
Click to expand...
Click to collapse
Hi Exiatron00,
got it working somehow!!!!
Bought a 3 day licence for DC Phoenix where you are able to put Firmware even in fastboot with FRB lock and no USB Debugging on.
So I got the IMEI and Fitting Version which is a L11.
Downloaded it original from Huawei as I still want a original stock Rom not customized which was
HUAWEI P9 Lite Firmware (VNS-L11, Android 6.0, EMUI 4.1, C432B161, WEU) only wokring one.
BUT the big Problem is that the apk Android System Web View is missing in the ROM. A known Problem by HUAWEI. Yeah now I am stucking in the Setup wizard like this guy who mentioned also the solution whell the reason of this Problem.
https://forum.xda-developers.com/hu...stuck-initial-setup-upgrade-to-t3498097/page2
So my question now. How do I get the apk on the phone still no USB Debugging? Does anyone have this Version original incl. this apk? Maybe an img. from a running working System?
Only way I am able to put the Firmware on is DC-Phoenix. It is valid still two days. Maybe someone can help me? Please?
So an Image of VNS-L11, Android 6.0, EMUI 4.1, C432B161, WEU incl. Android System Web View, so that I can go ahead and use the phone again please?
Thanks a lot.
Kind Regards.
Hello people!
I've been doing installation of custom ROM and any kind of configuration for a while now. But I have now in my hands a tough problem. My dad bought athene XT1640-DS (Moto G4 Plus), just like the one of mine own, but mine doesn't have the '-DS'.
But the device is stuck at Stock Android 6.0.1 and I can't update it.
The USB seems have some problem because any PC in my house recognize the 6.0.1 phone, but works fine with my up to date 8.1.0 athene, but it's charging only, and the turbo charging isn't working. the fingerprint isn't working neither.
It looks like the bootloader was unlooked, because everytime it's turned on shows the 'bootloarder unlock message'. But I was unable to root it, I tried all the one click root apps, but none of them worked.
It doesn't have any custom recovery, so I tried to update with the stock recovery but every OTA Blur Version rom that I found for athene shows a error telling that my ROM version isn't compatible with the updates (the ROM version code of this phone is MPJ24.139-23.1/ 1 user).
Anyone have any hints of what can I do to update this device?
Device XT-1640-DS
Android: 6.0.1
M8952_7000.04.03.32R
ATHENE_BRAZIL_DSDS_CUST
Kernel: 3.10.84-GCF01273
[email protected] #1
MPJ23.139-23.1
From what I know one click methods doesn't work with this device. You need a proper kernel for android 6.0 like elementalx 1.0. And supersu or magisk zip flashed through a recovery like TWRP.
Is there a way to update de kernel, or do that other things without PC and root?
Or a way to use adb without USB connection?
Have you tried fastboot flash methods like in this thread?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
So.. the big issue is that this device isn't connecting to the PC, it's charges, but neither the PC not the Android show any signs that their are connected. I can't use adb from the PC because I couldn't make the computer recognize the phone.
can you at least transfer files in mtp mode with the usb cable? because looks like the micro usb port is messed up.
If you are on warranty period you should go for it
I can't use the mtp neither. The only thing I can do is charge. And I'm out of warranty :/
Hey! This is my first time here, sorry if I'm doing smth wrong, I just really need help. My fossil gen 6 is kinda useless at this point after updating to Wear OS 3 and I would like to flash it back to Wear OS 2, since I don't get any notifications & I can't even sync my notes at this point without connecting to wifi (not even through mobile data, which is pretty annoying -> my phone & watch doesn't connect to each other through bluetooth)
thanks, for any guides in advance!
night
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
edwin270 said:
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
Click to expand...
Click to collapse
Did that 3 times already, nothing changed. Thanks for your answer though!
Did you get anywhere with this? I also want to go back to wear os 2. I hate the fossil app
I'd like to know too. I just came back to Android with the S23 Ultra and wanted to pair my Razer x Fossil watch to it. But I decided to update since I was doing a factory reset/disconnect anyways. Big big BIG mistake.
There has to be a way to flash wear OS 2.3 back to the watch and re partition it as stock. I'm able to see my watch as a USB perhp on my machine without BT or wifi connection.
Anyone have the old firmware for these watches? Short of buying another Razer watch for $600
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
MiamKebab said:
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
Click to expand...
Click to collapse
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Or would you be able to provide some guidance on how to proceed?
Arkbird1000 said:
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Click to expand...
Click to collapse
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
MiamKebab said:
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
Click to expand...
Click to collapse
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
You guys seems way ahead on me in the downgrade process...
I made Wear OS 3 update but the Fossil app used to pair the watch won't work with Oneplus 8 Pro (Android 13), gotta go back but i have no idea how...
Yet i flashed a lot of custom roms and stuff in the past, but now.. kinda lost
Im looking forward to see news here
Good luck guys, i'll keep updated if i somehow manage to flash the OTA posted ahead
Edit : well i was on Apkmirror to try an older apk of the app, and found out their app targets android 12 but not android 13..........
Arkbird1000 said:
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
Click to expand...
Click to collapse
I do have the TWRP but need to find it, took some tweaks from Ticwatch 3 pro. I didnt pushed it on the repo tho. I didnt what made me do it, but I wiped my system partitions and had to rebuilt from the OTA only. But after getting the watch working again, I had few functionalities broke, including the OTA updates. If you can social enginner your way thru fossil to get files such as stock rom and other files for qualcomm software like rawprogrammer and firehose files it can be great help.