i wrongly installed stratos version on the verge version !
now i have installed the verge version ack but i dont have touch in the watch
what do i need to do how can i fix it?
can i?
where can i get older versions?
mstrolo said:
i wrongly installed stratos version on the verge version !
now i have installed the verge version ack but i dont have touch in the watch
what do i need to do how can i fix it?
can i?
Click to expand...
Click to collapse
You will have to find the original Rom/firmware and flash that back onto the watch...search the internet it has to be somewhere...'.
am trying for the last couple of hours and nothing
can it be hardware?
after installing the wrong firmware can it destroy the hardware?
caz the phone comes up but i dont have any touch just shows me the scan code
and i cant confirm it
Damoedge said:
You will have to find the original Rom/firmware and flash that back onto the watch...search the internet it has to be somewhere...'.
Click to expand...
Click to collapse
if i will install the original firmware you think the rouch will work ?
mstrolo said:
can it be hardware?
after installing the wrong firmware can it destroy the hardware?
caz the phone comes up but i dont have any touch just shows me the scan code
and i cant confirm it
Click to expand...
Click to collapse
Could be... But first calm down. What do you mean by "the phone comes up but i dont have any touch just shows me the scan code
and i cant confirm it"?
You mean watch? If watch is showing the scan code, that's good. Take your phone, delete any amazfit watch under Bluetooth, clear amazfit app data, login again and then try to scan the watch with the app.
Sent from my CMR-W09 using Tapatalk
Zeljko1234 said:
Could be... But first calm down. What do you mean by "the phone comes up but i dont have any touch just shows me the scan code
and i cant confirm it"?
You mean watch? If watch is showing the scan code, that's good. Take your phone, delete any amazfit watch under Bluetooth, clear amazfit app data, login again and then try to scan the watch with the app.
Sent from my CMR-W09 using Tapatalk
Click to expand...
Click to collapse
sorry yea i meant the watch...
the touch is not responding to anything
the watch only responds to commands via adb
this is where i am
mstrolo said:
sorry yea i meant the watch...
the touch is not responding to anything
the watch only responds to commands via adb
Click to expand...
Click to collapse
But it's showing qr code? That's normal behavior. Watch has to be paired first. Please try what I've suggest above.
But first, calm down. Panicking is not helping at all. You can even make it worse ?
Sent from my CMR-W09 using Tapatalk
you see the watch comes up but icant press it touch not working
https://www.youtube.com/watch?v=eXdmOlCyF3U&feature=youtu.be
just like what he is heving on his watch but mine is the verge
Zeljko1234 said:
But it's showing qr code? That's normal behavior. Watch has to be paired first. Please try what I've suggest above.
But first, calm down. Panicking is not helping at all. You can even make it worse
Sent from my CMR-W09 using Tapatalk
Click to expand...
Click to collapse
look at the video
AFAIK Verge INTL firmware only supports one language, so it goes directly to QR code for pairing after it's started up. You may need to do a full wipe of storage before flashing stock Verge firmware for your watch model (I recommend using the same version that was installed originally on your watch: A1801 = CN, A1811 = INTL). If you know how to flash the firmware manually from bootloader, you can erase user data while in fastboot mode:
Code:
fastboot erase data
fastboot erase cache
fastboot erase userdata
if it fails, you may want to also erase system, but after doing this the watch will not boot until you flash a firmware manually, so pay attention to what you do!
Code:
fastboot erase system
After erasing, you can flash the firmware by booting the modified recovery partition with root access, then proceed with manual firmware installation:
Code:
fastboot boot modified_recovery.img
i enterd the twrp and touch is working so its just a software thing
have any idea what i need to do?
lfom said:
AFAIK Verge INTL firmware only supports one language, so it goes directly to QR code for pairing after it's started up. You may need to do a full wipe of storage before flashing stock Verge firmware for your watch model (I recommend using the same version that was installed originally on your watch: A1801 = CN, A1811 = INTL). If you know how to flash the firmware manually from bootloader, you can erase user data while in fastboot mode:
Code:
fastboot erase data
fastboot erase cache
fastboot erase userdata
if it fails, you may want to also erase system, but after doing this the watch will not boot until you flash a firmware manually, so pay attention to what you do!
Code:
fastboot erase system
After erasing, you can flash the firmware by booting the modified recovery partition with root access, then proceed with manual firmware installation:
Code:
fastboot boot modified_recovery.img
Click to expand...
Click to collapse
the touch is working on twrp
so its just a software issue
but i need to fix it some how
mstrolo said:
look at the video
Click to expand...
Click to collapse
It was the same when stitching the recovery from Stratos for firmware 3.2.0.5. The twrp recovery firmware helped. The sensor earned, after I flashed the original Chinese firmware 3.0.12.0 and the recovery was replaced with the stock one. Everything is working
yea i flashed the new twrp and the touch is working
thanks for the help
i can breath hhh
mstrolo said:
yea i flashed the new twrp and the touch is working
thanks for the help
i can breath hhh
Click to expand...
Click to collapse
If you do not reflash twrp to stock recovery, then OTA updates will not work for you
Now I see.
So, you flashed Stratos ROM on your Verge.
Can you check your bootloader status? I guess it's unlocked if you booted TWRP. What ROM do you have installed now in the watch? Do you still have the Serial Number?
Related
Hard brick for OPT happens when you change critical partitions. It will follow improper firmware flash or accidental erase of certain partitions. The phone won't show any response when hardbricked.
The solution for OPT is similar to OPO - you just need a Qualcomm driver and a recover package. The only full recovery package available is very big and it restore the phone to Hyrdogen OS, with everything wiped. So it would not be very attractive.
Fortunately, thanks to this post from Chinese supporting forum, a minimal version of restore package is provided. It does not wipe user data and guarantee a recovery entry. you would normally be freed using this package. if not, please use the full package in the end of the post
Download link for driver
Download link for Recovery tool
uncompress the files to a local folder.
First step, turn off drive signature enforcement in windows 8/8.1/10. Tutorial Here
Second step, hold the power key for 20 seconds to force turn off power. connect OPT to usb, hold volume+ and power until your PC finds a new hardware (if it doesn't work, try hold volume+ and volume- together)
Third step, go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics 9006" device. Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Fourth step, when the driver is installed properly, run MSM8994DownloadTool.exe in the recover tools folder, using admin privileges . Clear start in top left corner and wait for it to finish.
Now your OPT should be able to enter TWRP recovery. It still won't boot but you can manually flash anything again (like the full Oxygen OS package).
The procedure is tested by me twice. Enjoy!
p.s: sorry the recovery image in the A2001_save_brick_mini.rar is Chinese. Please download this file, change the name to recovery.img and substitute the file in the recovery tool before flashing.
UPDATE：full Oxygen OS 150805 restoration package for those who experience recovery entry problem. Note that this package wipes everything including internal storage!
Awesome, I will go ahead and make a full recovery tool that includes these files as well as the latest version of OxygenOS as I did with the Oneplus one.
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
CoreGaming said:
You write about a full Oxygen Package? What do you mean with it? a flashable .zip or fastboot .img?
Click to expand...
Click to collapse
Like i did before with my mod of the toolkit
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
okay and were can i get this package for the OPT?
CoreGaming said:
okay and were can i get this package for the OPT?
Click to expand...
Click to collapse
Havn't made it yet, still need to work on it. It is a little different than OPO so it might take some time.
okay this will be great. Take your time i'm ready
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Lord Boeffla said:
Hi,
anyone knows how I can force the OnePlus Two to enter QUALCOMM-HS mode?
I have a "semi-bricked" OP2.
It can boot, but the recovery is broken and I cannot enter it anymore. Worse enough, the bootloader is locked and I cannot unlock it anymore.
So I am kinda stuck and thought this manual would bring me back recovery. But - I cannot get it to enter this specific emergency recovery mode as boot loaders are intact.
Any idea?
Thanks
Andi
Click to expand...
Click to collapse
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Zyxxeil said:
Hmm, I may be able to help. Do you got a hangouts we can talk on so it could be easier? If so PM me your email so I can add you.
Click to expand...
Click to collapse
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Click to expand...
Click to collapse
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Andi
Lord Boeffla said:
Hi,
ok, I am one step further now.
I could bring the device in that mode, flashed via this recovery tool. All partitions were flashed but still no recovery. How can that be? ooops.
I did that many time on my OPO already successfully. But of course with the full recovery package.
So question is, I would not mind starting from scratch... anybody knows where the "big" recovery package that erases everything is available?
Thanks
Andi
Click to expand...
Click to collapse
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Lord Boeffla said:
I am on Oxygen 2.0.1 and still do not have the option. Something is really odd...
Click to expand...
Click to collapse
HydrogenOS definitely has the option because it is how I flashed TWRP in the first place
khr0n0s said:
I'm in a similar situation to you. I lost my recovery and somehow my boot loader is locked again. I can't set OEM unlock as I am on the old version of OxygenOS.
I tried the above instructions but they don't work. The phone reboots as normal, not in to recovery. If you solve this then let me know.
EDIT: I think flashing hydrogenos using this method is the best idea. We can then select the OEM unlock from developer settings, use fastboot to unlock the bootloader and flash a new recovery. The question is how? @qwsdert4
Click to expand...
Click to collapse
Without recovery how do you flash hydrogenOS?
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Wow thanks, I was trying to do it with the one you posted but I couldn't since it was missing the info for system sectors. Now i can make my tool
Zyxxeil said:
Without recovery how do you flash hydrogenOS?
Click to expand...
Click to collapse
Using this tool and the full recovery package? Or am I missing something here?
khr0n0s said:
Using this tool and the full recovery package? Or am I missing something here?
Click to expand...
Click to collapse
The tool posted does not contain a system, but he is going to post the full one soon.
Zyxxeil said:
The tool posted does not contain a system, but he is going to post the full one soon.
Click to expand...
Click to collapse
Precisely, that is exactly what I meant. Fingers crossed that will solve this.
It could be I successfully recoverd following a hint by user @Zyxxeil (many thanks for the help).
If all works I will post soon what I did.
But - have everything running now again. Next I try to flash twrp again and root. If that worked, I will post the steps.
Andi
qwsdert4 said:
Hi, I got the "big recovery package" in question from OP support centre in China. It will recover your OPT to factory Hydrogen OS from which you could start over. I'll upload it onto Mega very soon so stay tuned.
Click to expand...
Click to collapse
Very nice. Wait for it...
Is a Version with Oxygen OS also aviable?
Welcome to Twrp 3.0.0.0 for our Zenwatch 2's
This release I was able to flash the recovery, flash the supersu zip, and flash some others, so far I have not encountered our wild soft brick madness.
Thanks to @acbka for showing me how to get into log files, essentially helping me figure out why the partitions were not mounting correctly when I compiled and recompiled.
Here is TWRP 3.0.0.0
Directions:
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot flash recovery twrp3.img
OR load up your tethered twrp and flash the image under that.
Hope you guys enjoy! So far I have not encountered soft bricks so it should be safe and sound
thank you, will test now
---------- Post added at 09:21 PM ---------- Previous post was at 09:01 PM ----------
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
okaay3D said:
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
Click to expand...
Click to collapse
That im not sure, it might, wouldnt hurt to fastboot boot it and see if itll start twrp. I have the 501
Root will go with modifying the Momentum kernel so you wont have much lag on the watch, and any other root modifications that can go with it, like maybe xposed?
Next step in development is fixing twrp so it can be flashed, then maybe modifying the wear os? Or maybe porting some stuff
T10NAZ said:
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting
Click to expand...
Click to collapse
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
matze19999 said:
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Click to expand...
Click to collapse
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Awesome! Got supersu flashed and was able to use Advanced Settings to disable some of the built-in bloatware apps. I'll have to try out the kernel but I'm currently at work and don't want to spend all day messing around with my watch (well... I want to, but I like not getting fired).
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I do have the 5.0.1 wear downloaded and installed! And as far as i know, Its working ok
okaay3D said:
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
Click to expand...
Click to collapse
You can tell twrp to preserve the system protection, back every single thing up that you can in the twrp option, push that backup to your computer, and then you can disable system protection. twrp itself wont do anything, however playing with options will modify the watch.
OR you can fastboot pull things off the watch, the system.img and boot.img yourself, in case the ones uploaded in my general thread didnt have the protection enabled.
If you want to hang tight until 1.4 comes out, that can be a good thing too
And im not sure if there is something like that on the watch. I have not seen anything about it before
My attempt was a failure on my WI502Q. I got the following messages. And, OP, how do you pull system.img from a device through fastboot? I thought you needed root permission to do that through adb.
"
C:\adb\zw2>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.834s
"
Thanks for this! I was losing hope on any development for this watch but now we have the most crucial component to modifying anything on android, a custom recovery. Going to perform a backup, root and flash your custom kernel you kindly released as well!
T10NAZ said:
Hello everyone, I have been working hard last night to make twrp run on our watches, and this I think is a good representation on what itll be like with actual development going on
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting, and I was able to flash some zips and kernels successfully, and I fixed the UI to look better and actually usable on the watch
Also, I was able to flash this puppy, and I got android wear to boot with it flashed, however most of the time, it goes haywire and only boots into recovery. Same thing applies, this shall be a Tethered recovery only until I know why its going crazy.
As always, problems can arise on your watch, so be careful!
read the entire instructions, This is a known way to get system protection off, and to flash zips/kernels when need be. Do not flash please.
Here is the link to the updated twrp
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot boot recovery.img like the other one.
I also have a kernel underway if people would like to try it out and test it in the next couple days
Click to expand...
Click to collapse
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
yash92duster said:
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
Click to expand...
Click to collapse
it could lead to that, yea, since this is the only root method basically, it adds a few extra steps to do it
can we root with regular supersu .zip, or do we need a special build for wear devices?
slothdabski said:
can we root with regular supersu .zip, or do we need a special build for wear devices?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view?usp=sharing there ya go. dunno if the regular supersu works. havent tried that out. this one does. and alrdy has a busybox installer wear app included which u need anyway sooner or later.
there is no supersu manager app in it though like on phones. apps requiring root just have it. tested advanced settings so far for disabling built-in stuff and a reboot option. but maybe there is a supersu-wear.apk somewhere?
not my link. taken from here: http://forum.xda-developers.com/showpost.php?p=65759835&postcount=14 he took it from the G watch R forums iirc.
zenwatch2
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
mehdi.ahmadi said:
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
Click to expand...
Click to collapse
Let me know the steps you took from when you downloaded it, to when it sits on the asus logo, and do you have the 502 or the 501 watch?
mehdi.ahmadi said:
after the flash twrp recovery
Click to expand...
Click to collapse
guess that means he flashed it. now his watch is bricked. not that it hasent been mentioned NOT to flash it just fastboot boot ...
flash the stock images via fastboot or tethered (NOT flashed) twrp and you should get your watch working again.
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
matze19999 said:
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Click to expand...
Click to collapse
found it about 2 weeks ago somewhere here on xda and alrdy linked it to several ppl here in the thread.
but thx
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
totib38 said:
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
Click to expand...
Click to collapse
Make sure you have the latest sdk platform tools, r28.
Then download the factory image again, it might have been corrupted. Use 7zip to extract the zip file.
Flash the factory image again using the flash-all batch file. Note, this will wipe your device.
If that doesn't work then you might have a hardware issue.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Make sure you have the latest sdk platform tools, r28.
Then download the factory image again, it might have been corrupted. Use 7zip to extract the zip file.
Flash the factory image again using the flash-all batch file. Note, this will wipe your device.
If that doesn't work then you might have a hardware issue.
Click to expand...
Click to collapse
Thanks for your answer.
I will retry tonight at home.
One more detail : so I have to modified flash-all batch file ?
In some discussion I saw some people delete -w of the script.
I will inform if the process is ok
totib38 said:
Thanks for your answer.
I will retry tonight at home.
One more detail : so I have to modified flash-all batch file ?
In some discussion I saw some people delete -w of the script.
I will inform if the process is ok
Click to expand...
Click to collapse
If you delete the -w it will not wipe your device. You can try that, but if problem still is there then include the -w. Wiping your device is a better trouble shooting solution but you will have to setup your device like it was new. It's up to you.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks for your support.
I just tried several flash factory image but the result is always the same.
I can't turn on wifi setting ....
Everything else seems to work.
I'm really disappointed and I don't know what to do.
It seems there is a issue with vendor.img
After my first boot, I download Es explorer and I navigate in :
'System>vendor>ECT>wifi' and it seems files are missing compare to my others devices.
Is there a way to modify the field with root permission?
Maybe you need to unlock the critical partition before flashing?
gm007 said:
Maybe you need to unlock the critical partition before flashing?
Click to expand...
Click to collapse
Hello gm007
How can I unlock the critical partition before flashing ?
Thanks by advance ?
totib38 said:
Hello gm007
How can I unlock the critical partition before flashing ?
Thanks by advance ?
Click to expand...
Click to collapse
fastboot flashing unlock_critical
Not sure if it's needed.
this will wipe ur phone same as unlocking bootloader.
gm007 said:
fastboot flashing unlock_critical
Not sure if it's needed.
this will wipe ur phone same as unlocking bootloader.
Click to expand...
Click to collapse
It's failed...
It's indicate 'Invalid argument unlock_critical'
totib38 said:
Thanks for your support.
I just tried several flash factory image but the result is always the same.
I can't turn on wifi setting ....
Everything else seems to work.
I'm really disappointed and I don't know what to do.
It seems there is a issue with vendor.img
After my first boot, I download Es explorer and I navigate in :
'System>vendor>ECT>wifi' and it seems files are missing compare to my others devices.
Is there a way to modify the field with root permission?
Click to expand...
Click to collapse
I don't know what you're seeing in the etc folder but this is what I have in the pixel 3,
jd1639 said:
I don't know what you're seeing in the etc folder but this is what I have in the pixel 3,
Click to expand...
Click to collapse
Ah .....
Ok so the vendor.img should be ok.
I'm completely lost .
Everything works except that. And the phone has just a week so I don't think it's a hardware issue.
If I don't find the solution i will keep this device in my desk ?
totib38 said:
Ah .....
Ok so the vendor.img should be ok.
I'm completely lost .
Everything works except that. And the phone has just a week so I don't think it's a hardware issue.
If I don't find the solution i will keep this device in my desk [emoji25]
Click to expand...
Click to collapse
Did the wifi work when you first got the phone? When you flashed the factory image did you wipe the device or use the flash all with the -w removed? If you wiped the device I'm guessing it is a hardware issue.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Did the wifi work when you first got the phone? When you flashed the factory image did you wipe the device or use the flash all with the -w removed? If you wiped the device I'm guessing it is a hardware issue.
Click to expand...
Click to collapse
Yes the wifi worked at the first boot.
I'm guessing I have wipe the device and that's the reason wifi there is a problem.
Is there any way to recover wifi drivers or anything else ?
What are my possibilities ?
Go on a sav and change wifi hardware ?
totib38 said:
Yes the wifi worked at the first boot.
I'm guessing I have wipe the device and that's the reason wifi there is a problem.
Is there any way to recover wifi drivers or anything else ?
What are my possibilities ?
Go on a sav and change wifi hardware ?
Click to expand...
Click to collapse
I don't know how flahing the factory image would cause the problem. But a couple of things to check. First, make sure you're using the latest sdk platform tools (fastboot and adb), r28. Then make sure you're using the correct factory image, there one for docomo or something like that which is for the Japanese variant, and redownload it in case you got something corrupted.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I don't know how flahing the factory image would cause the problem. But a couple of things to check. First, make sure you're using the latest sdk platform tools (fastboot and adb), r28. Then make sure you're using the correct factory image, there one for docomo or something like that which is for the Japanese variant, and redownload it in case you got something corrupted.
Click to expand...
Click to collapse
I will try again tonight but I have no hope
I use the last SDK platform tools r28.0.1
And I took the factory image from google devs website.
My Mac address is block on 02:00:00:00:00:00 to be more precise.
totib38 said:
It's failed...
It's indicate 'Invalid argument unlock_critical'
Click to expand...
Click to collapse
Seems you have outdated sdk try to remove and install the latest one as suggested above. Or try another pc.
gm007 said:
Seems you have outdated sdk try to remove and install the latest one as suggested above. Or try another pc.
Click to expand...
Click to collapse
It Is not because fastboot flashing unlock_critical is a command for pixel 3 XL ?
I got the pixel 3 device
totib38 said:
Hello everyone.
I'm new in the forum and I'm looking for help.
Habitually I try to solve my problems by myself but this time I need your help.
I recently acquired a pixel 3. And everything works fine until I had to flash the factory image.
I find the factory image file on google dev website and I follow the instructions.
I also tried different tutos but I always have the same issues.
My pixel 3 restart but I can't turn on WiFi.
My Bluetooth is ok
Finally, it feels like the pixel is more slowly since I flash the factory image. (Setting app crash half of the time).
Is anyone had the same issues or have a solutions ?
Thanks by advance.
Click to expand...
Click to collapse
I think you're platform-tools are not up to date. Download them from here:
https://developer.android.com/studio/releases/platform-tools
Put the facrory image in the same folder as the platform-tools and execute flash-all from there.
I thougt mine were up to date, but not everyting from the image got flashed.
With the latest platform tools everyting was ok.
rhino666 said:
I think you're platform-tools are not up to date. Download them from here:
https://developer.android.com/studio/releases/platform-tools
Put the facrory image in the same folder as the platform-tools and execute flash-all from there.
I thougt mine were up to date, but not everyting from the image got flashed.
With the latest platform tools everyting was ok.
Click to expand...
Click to collapse
Thanks for your help.
This is precisely the one I took yesterday and I always have the same issues
totib38 said:
Thanks for your help.
This is precisely the one I took yesterday and I always have the same issues
Click to expand...
Click to collapse
Then the only thing I can think of is for you to try another cable or computer.
Hello dear fellow mido users. I am trying to solve a problem here and I would very much appreciate your help on this:
I am running latest MIUI Stable Global flashed from fastboot, I have IMEI, but I don't have mobile signal. WiFi & BT works fine.
How I got here:
Bricked the phone about half a year ago
Ressurected it a week ago via connecting the pins in the back and flashing via edl.
I have unlocked it officially, as I had it unlocked before.
I have flashed TWRP & latest official RR, but it bootlooped, because my /persist partition was freaked out, so I reflashed it from the extracted fastboot ROM and I booted.
However, both my IMEIs dissappeared, and I only had the first IMEI from the back of my phone. So I calculated the second IMEI per a tutorial (from a Czech site) and restored both IMEIs via the Qualcomm QPST xqcn file, verified both IMEIs are showing up on my phone and are valid as per online IMEI checkers.
However, the signal didn't work, so I reflashed another mido device's IMEI (I have my original IMEIs backed-up) and flashed latest MIUI fastboot ROM, still no signal.
And here I am, and I am asking you for help..
If anyone can help me or at least point me in the right direction I will be eternally grateful :angel:
Bump, offering $5 PayPal to anyone who helps me restore my mobile signal.
JouzaCZ said:
Bump, offering $5 PayPal to anyone who helps me restore my mobile signal.
Click to expand...
Click to collapse
"Ressurected it a week ago via connecting the pins in the back and flashing via edl." - are you sure you didn't accidently disconnect the antenna cable from the motherboard end or from the USB board end while doing the tespoint connection to get into EDL mode?
crok.bic said:
"Ressurected it a week ago via connecting the pins in the back and flashing via edl." - are you sure you didn't accidently disconnect the antenna cable from the motherboard end or from the USB board end while doing the tespoint connection to get into EDL mode?
Click to expand...
Click to collapse
Thank you so much for your reply. I just checked, the cable wasn't disconnected, but I dis-and-reconnected it just to make sure. Still no signal.
I should mention I reflashed my original IMEI and verified that its valid once again. I am attaching links to pictures of the back of my phone disassembled if anyone can spot something wrong: PHOTOS.
Still hoping for a solution.
JouzaCZ said:
Still hoping for a solution.
Click to expand...
Click to collapse
Okay, starts to be interesting. Did you play with the band selection? Probably the band has been changed to US?
Hope you have Magisk (root) - if not please flash Magisk.
I presume ADB is already installed.
Put the phone to airplane mode.
From a PC open a cmd and issue adb shell
or start a terminal emulator on your phone
Then issue these commands in the shell
su
pm clear com.android.providers.telephony
settings put global preferred_network_mode 10
settings put global preferred_network_mode1 10
settings put global preferred_network_mode2 10
Remove airplane mode.
Restart.
Check again.
If still not works:
Start phone in fastboot mode
Issue these commands from PC cmd:
fastboot devices << just to make sure you phone is recognised
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
It will restart.
Check again.
Anyway, if you issue *#*#INFO#*#* or better known as *#*#4636#*#* in the dialer then selecting Phone 1 or Phone 2 (according to the SIM slot you want to check) in the top right or lower left there is a band-select menu (not in MIUI but in other custom ROMs) so there you are able to select the correct band if you want (that would mean you flash any custom ROM from TWRP or any custom recovery for a couple of minutes, go to dialer and look around)
crok.bic said:
Ping
Click to expand...
Click to collapse
Tried everything you said in order, still doesn't work. In normal fastboot, fastboot erase modemst1 results in this image isn't allow download. So I used mfastboot and it worked, however still no signal. When I try to switch the band in the options menu, there are two options: Automatic and United States. When clicked, both result in: Set [United States/Automatic] Unsuccessful.
And I just noticed it erased my IMEI again... Maybe the IMEI wasn't really there the whole time?
What is the proper way to flash both IMEIs? (I know them both)
JouzaCZ said:
Maybe the IMEI wasn't really there the whole time?
What is the proper way to flash both IMEIs? (I know them both)
Click to expand...
Click to collapse
I have the impression that the IMEI wasn't even there..
Flashing it is not possible.
The partition called EFS - in TWRP - is the one storing these kind of IDs.
If you have a backup of EFS you are good to go.
I used to tell people that before doing anyhing (before even unlocking the bootloader)
just do QCN info backup so in case of IMEI / Wifi MAC / Bluetooth MAC issues it's easy to restore..
Your case is a bit more advanced since you have no backup - so you have only one way to get out from this situation:
re-generate the QCN info. I advise you to use >>this<< tutorial (files are attached to the post) to properly re-generate and push back the correct info.
And here's the ultimate guide as well: part 1 and part 2
crok.bic said:
I have the impression that the IMEI wasn't even there..
Flashing it is not possible.
The partition called EFS - in TWRP - is the one storing these kind of IDs.
If you have a backup of EFS you are good to go.
I used to tell people that before doing anyhing (before even unlocking the bootloader)
just do QCN info backup so in case of IMEI / Wifi MAC / Bluetooth MAC issues it's easy to restore..
Your case is a bit more advanced since you have no backup - so you have only one way to get out from this situation:
re-generate the QCN info. I advise you to use >>this<< tutorial (files are attached to the post) to properly re-generate and push back the correct info.
And here's the ultimate guide as well: part 1 and part 2
Click to expand...
Click to collapse
Okay, I have already followed the first tutorial you linked before, so I have the xQCN files ready. I will follow the second tutorial and report back. Thank you for taking the time to help me.
JouzaCZ said:
Okay, I have already followed the first tutorial you linked before, so I have the xQCN files ready. I will follow the second tutorial and report back. Thank you for taking the time to help me.
Click to expand...
Click to collapse
After that I advise you to use MiFlash and flash a recent fastboot ROM.
Report back when you finished. There should be a way..
crok.bic said:
After that I advise you to use MiFlash and flash a recent fastboot ROM.
Report back when you finished. There should be a way..
Click to expand...
Click to collapse
Okay, I followed the first tutorial and successfully restored both IMEIs, still not working. I noticed, while flashing the xQCN file, it gives me a message about the model number of the phone not matching the model number of the xqcn file. Is that normal?
Last resort is to follow the second tutorial and redo everything.
JouzaCZ said:
gives me a message about the model number of the phone not matching the model number of the xqcn file
Click to expand...
Click to collapse
Waitaminute.. What is the error message exactly? This is odd, I used that file many times without any glitch, issue or error message.
crok.bic said:
Waitaminute.. What is the error message exactly? This is odd, I used that file many times without any glitch, issue or error message.
Click to expand...
Click to collapse
"The model number in the QCN file and the phone do not match. Do you still want to restore the phone with this file?"
JouzaCZ said:
"The model number in the QCN file and the phone do not match. Do you still want to restore the phone with this file?"
Click to expand...
Click to collapse
In fastboot mode what is the answer of the phone to the command adb devices and fastboot getvar product? I don't care about the serial but all the rest.
crok.bic said:
In fastboot mode what is the answer of the phone to the command adb devices and fastboot getvar product? I don't care about the serial but all the rest.
Click to expand...
Click to collapse
fastboot getvar product: mido
adb devices: 7e03cac30903 device
JouzaCZ said:
fastboot getvar product: mido
Click to expand...
Click to collapse
Something is not quite straight here - the QCN file there is for Mido, that's 100% sure.
You started the thread with this statemenet: "Bricked the phone about half a year ago"
What did you do exactly? Once I had a phone - remotely resurrected - that has been flashed with a markw ROM (Redmi 4X) instead of Redmi Note 4X (mido) and the guy experienced something similar.
crok.bic said:
Something is not quite straight here - the QCN file there is for Mido, that's 100% sure.
You started the thread with this statemenet: "Bricked the phone about half a year ago"
What did you do exactly? Once I had a phone - remotely resurrected - that has been flashed with a markw ROM (Redmi 4X) instead of Redmi Note 4X (mido) and the guy experienced something similar.
Click to expand...
Click to collapse
Pasting from a thread I made back when I bricked the phone:
Here's the situation:
Was on stock MIUI Global 9.5.8.0 with RedWolf Recovery.
Did a backup and flashed LineageOS
Wasnt happy with it and flashed back the backup, including the Firmware and EFS partitions, basically every partition
Bootloop, WiFi and BT driver prolly messed up, cant connect and restarts upon trying to connect to WIFI/BT.
Tried flashing other firmware, various combinations of wipes, flashes, MiFlashTool fastboot rom, nothing helped.
Tried flashing with EDL, the newest ROM gives me "Too many lines in XML file", old ROM flashed fine, but then couldn't even get to fastboot.
Now: Can't get to fastboot nor recovery, phone goes to EDL mode w/ red LED blinking when connected to PC.
QFIL gives me "Cannot read packet header, read 0 bytes", same with MiFlash.
Click to expand...
Click to collapse
JouzaCZ said:
Was on stock MIUI Global 9.5.8.0 with RedWolf Recovery.
Did a backup and flashed LineageOS
Click to expand...
Click to collapse
Do you have this backup you made with RedWolf?
JouzaCZ said:
including the Firmware and EFS partitions, basically every partition
Click to expand...
Click to collapse
Not a good move. System is up and running, tho, right?
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
crok.bic said:
Do you have this backup you made with RedWolf?
Not a good move. System is up and running, tho, right?
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
Click to expand...
Click to collapse
Don't have the backup.
Sorry for confusing you, the Now section is from the old post, I haven't done anything since my last post.
JouzaCZ said:
Pasting from a thread I made back when I bricked the phone:
Click to expand...
Click to collapse
JouzaCZ said:
Don't have the backup.
Sorry for confusing you, the Now section is from the old post, I haven't done anything since my last post.
Click to expand...
Click to collapse
No worries - but still:
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
crok.bic said:
No worries - but still:
If you go to Settings - About phone - Baseband - what is the baseband version?
Does it looks like a decent version info or say "unknown"?
Click to expand...
Click to collapse
Decent version. Specifically: 953_GEN_PACK-1.148143.1.163979.1
Also can we switch to some IM like WhatsApp so we don't have to keep pinging each other via quotes? I will post the solution/result in the thread.
Hello, I'm fairly new here. I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV Box: https://www.androidtv-guide.com/pay-tv-provider/united-group-eon-ott-smart-box/
Fzloop said:
Hello, I'm fairly new here.
Click to expand...
Click to collapse
Fairly? You joined yesterday. You could hardly be fairer.
Fzloop said:
I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again.
Click to expand...
Click to collapse
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
Fzloop said:
How do i fix that?
Click to expand...
Click to collapse
One way is to flash the original recovery partition back to the device using burn mode.
Fzloop said:
How do i access the recovery mode?
Click to expand...
Click to collapse
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
goapy said:
Fairly? You joined yesterday. You could hardly be fairer.
The good news is that since it is bootlooping, the bootloader is probably okay.
For this model device running android 9, neither of the bootable partitions can be modified (while still running the original bootloader), even if the bootloader is unlocked, without causing a signature check failure. Since flashing some twrp version has modified the recovery partition, which is a bootable partition, the signature check is failing.
One way is to flash the original recovery partition back to the device using burn mode.
By holding the button on the device. You'll need the worldcup drivers and command line "update" burn mode tool (not the GUI burning tool).
If you have a copy of the original recovery partition, you'd just flash that with the update tool and be done.
If you don't have a copy of the original recovery partition, you can use the update tool to dump a different partition, like system, in order to learn which version of the firmware is installed on your box. Report the version here, and maybe some member will have the matching recovery partition that you can flash to your device using the update tool.
Click to expand...
Click to collapse
I did join yesterday, but I've been using this forum for a while without posting.
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Fzloop said:
I managed to fix the box on my own, turns out all i needed was an SD card and a ROM.
Click to expand...
Click to collapse
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
goapy said:
An alternative ROM, or the original ROM?
If you installed an alternative ROM, you may have "fixed" your box, but you've also blown away your drm keys forever.
If you're happy with the result, that's all that matters.
Although you could have posted that your issue had been resolved. That would have saved me from wasting my time. I always regret replying to posts about the dv8519. This is the last one for me.
Click to expand...
Click to collapse
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Fzloop said:
Unfortunately, alternative. I'm still looking for the original.
My apologies for wasting your time. Have a great day.
Click to expand...
Click to collapse
Hi @Fzloop,
can you share the ROM?
xfenixxx said:
Hi @Fzloop,
can you share the ROM?
Click to expand...
Click to collapse
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Fzloop said:
BoskoWifiBT
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Worked fine at first, but after playing with it a bit more the box just wouldn't boot, so be careful.
Click to expand...
Click to collapse
Thank you very much, I'll still give it a try.
Hello, I've tried flashing TWRP to my Android TV box, but now it's just constantly rebooting over and over again. How do i fix that? How do i access the recovery mode?
TV BOX https://www.androidtv-guide.com/pay-tv-provider/dhiraagu-tv-joybox/
box connected AMLOGIC usb burn tool. but error uboot/getresult/Diskinitial error