Database Info

Stuck at Motorola Dual-Core? [Wifi-Only]

Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!

On the real though, if you can get to Fastboot (or even the Moto "Android Recovery" state), you're not THAT bricked you've got to relock and go back to out-of-box; just keep a known-good boot.img around somewhere.

You just saved my life!

Thanks for sharing OP.
I take it this method is the same for 3.1?

I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Lcsglvr said:
I tried reverting back to stock using the "one click" root/unroot tool that was the first to come out for the Xoom.
Anyway, I tried the unroot process and everything was going fine, until something occurred. Now, it tries to boot up and says at the Moto Dual Core Technology screen, "Failed to boot LNX 0x0004 // Starting RSD mode 2".
Can someone help
Click to expand...
Click to collapse
Can anyone help!

Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
same here, anyone help ((

Lcsglvr said:
I hope this works. Although, I can't turn my xoom off. It also appears that my computer will not recognize my device when it is plugged in. In addition, I can't turn off my Xoom? It just reboots... so I can't enter fastboot mode.
I just posted this in a new thread.
Can anyone help!
Click to expand...
Click to collapse
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix

Honestly, I almost went through all of this last night when my WIFI Xoom got stuck in a boot loop.
However, I noticed that when my recovery went to flash the new 3.1 file, I felt like it didn't take as long as it should have. The file was the right size and all and it even said that everything installed successfully, but it just kept boot looping regardless of trying over and over. So I went ahead and re-downloaded the 3.1 file and repeated the steps to flash it and everything worked.
So, before you spend a whole lot of time restoring your Xoom, simply re-download the files and try it one more time. It worked for me.

rebill said:
You can still enter fastboot if you xoom won't shut off. Just hold the appropria oncete buttons as it reboot. Happened to me last night upgrading to 3.1. It. Wouldn't shut down at all. Once I got into fastboot my computer saw it and I was able to fix
Click to expand...
Click to collapse
Thanks! Finally have some hope to recovering. I'll post steps I took later once I get this damn thing fixed.

hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?

Lcsglvr said:
hmmm... I'm in fastboot supposedly and tried to flash boot.img but it seems to be stuck at <waiting for device>
This happen to anyone else?
After search seems like a driver issue, but I have installed the drivers... I was previous rooted, so I know I have the drivers. Just to be sure, I ran the MotoHelper again. I don't understand. It's just seeing my device on the "Starting Fastboot protocol support."
help?
Click to expand...
Click to collapse
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.

Hmm honesty. I'll give it a shot.
Sent from my ADR6300 using XDA App

Is the final OEM lock necessary? It's quite a pain as your userdata gets wiped if you unlock it...

I was stuck on bootloop, with unrecognised device, through adb was able to get back into clockwork recovery somehow at first boot, think twice down volume? Could be wrong.
I was able tto rreflash zip 3.1 over thet top again.
sry if this is different and unhelpful, bu imagine things are pretty desperate if you are considering returning the device

zerin said:
Yes. How did I fix it? I returned the xoom and had a new one two days later.
If the screen says something like "Entering RSD 2" then you're boned. The xoom won't be recognized in either the current state or in fastboot state by the computer, so no amount of commands will help. Even having the stock images doesn't help with that. Even RSDLite can't see the xoom in that state.
There have been several reports of people just being honest to Motorola and them fixing the device under the warranty.
Click to expand...
Click to collapse
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.

jbartcaps said:
You're not boned at all. I had that happen to me so I just got back into fastboot, downloaded the files in the OP put ADB, Fastboot and the adb extensions into the file I downloaded then ran the commands and got me XOOM back up and running fine.
Click to expand...
Click to collapse
You were likely in RSD 3, which is recognized by the computer. RSD 2 means adb and fastboot cannot see the device at all, so no flashing images is possible.
There's several states that all look very similar. Because some success was had with one doesn't mean it works for all. Motorola recognizes and is telling users that, in this state, the device needs to be sent back to them.

Can someone help us wifi xoom. Im stuck on the motorola screen and have a lil experience. I can fast boot reboot/fastboot device and it work but cant get the files from the hwi69 to fastboot on to it. I think im entering the commands wrong. Any advice would be appreciated

TheRedDroid said:
Hiya,
After dealing with a half-bricked Xoom, I did some research on this problem and found a solution.
If in any case, you happen to get stuck on the "Motorola Dual-Core Technology"
Solution to this (For the MZ604, One-Click rooted):
MZ604 Stock .imgs Download: http://developer.motorola.com/products/software/
*Make sure you have fastboot in the same directory as your adb for easy access*
1. Plug in your USB cord
2. Turn off your Xoom (Vol-Up + Power)
3. Boot into fastboot (Vol-Down + Power)
4. On your computer, open up a command prompt, and type the following:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
-or-
Code:
fastboot flash boot <path to boot.img>
fastboot flash system <path to system.img>
fastboot flash recovery <path torecovery.img>
fastboot flash userdata <path userdata.img>
fastboot erase cache
fastboot oem lock
5. Reboot the Xoom
Code:
fastboot reboot
6. There you go, back to stock!
Click to expand...
Click to collapse
Very good info to get into fastboot protocol:

Much thanks for the info. Worked like a champ. On an updated 3.2.1 XOOM I did an unlock, re-locked the wrong way, soft bricked, unbricked back to locked state. Finally followed your steps applied stock files and XOOM is re-locked and stock rocking back at 3.01. I needed to do all this to make sure I could get it back to stock in case it goes back to BB in 2 weeks. I was lucky enough to find one at a BB just not sure if I'll keep it. I plan on trying out some roms plus I heard Motorola is planning on doing an ICS push to the XOOM. ICS is very nice. It runs great on my unlocked Verizon G-Nex.. Again Thanks..

This post not only saved my half-bricked non-rooted Xoom, but also let me flash it from the Singapore firmware (bought if from Amazon, don't ask lol) to the regular USA firmware so that I can properly root it!
Thank you so very much!!

Razr Default Boots to Fastboot

Does anyone know the fastboot command to switch the default boot mode back to regular?

slayp00n said:
Does anyone know the fastboot command to switch the default boot mode back to regular?
Click to expand...
Click to collapse
Usually it will boot in fastboot mode if you have a bad flash. What is the message when the phone boots up?
Sent from my XT925 using Tapatalk 2

danifunker said:
Usually it will boot in fastboot mode if you have a bad flash. What is the message when the phone boots up?
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
stickybit factory_fastboot.
I never had a bad flash. I run cm10.1, but gps was not working someone said flashing stock then reflash cm10.1
So i used that stupid RSD LITE to flahs factory, all i did was fix the xml and erase the recovery flash. It worked fine the phone booted... Then I reflashed cm10.1 which works? Is there an oem command to kill the sticky bit?

I have tha solution!
slayp00n said:
stickybit factory_fastboot.
I never had a bad flash. I run cm10.1, but gps was not working someone said flashing stock then reflash cm10.1
So i used that stupid RSD LITE to flahs factory, all i did was fix the xml and erase the recovery flash. It worked fine the phone booted... Then I reflashed cm10.1 which works? Is there an oem command to kill the sticky bit?
Click to expand...
Click to collapse
excuse me for the next font and style, but I have a lot of time reading post forums and any track that help me to resolve this, and I found!! IN French but, no matter!!
To resolve the message and constantly booting into AP Fastboot, you need (into AP FASTBOOT MODE) put this command in your PC with fastboot
fastboot oem fb_mode_clear
Then press power and voilá... you phone boot normally...
:highfive:

:good::good::good:
alvaro_castro said:
excuse me for the next font and style, but I have a lot of time reading post forums and any track that help me to resolve this, and I found!! IN French but, no matter!!
To resolve the message and constantly booting into AP Fastboot, you need (into AP FASTBOOT MODE) put this command in your PC with fastboot
fastboot oem fb_mode_clear
Then press power and voilá... you phone boot normally...
:highfive:
Click to expand...
Click to collapse

this doesnt fix my issue with boot to bootloader.

atifsh said:
this doesnt fix my issue with boot to bootloader.
Click to expand...
Click to collapse
Well, does your fastboot screen have that message?
If not, what does it say?

killrhythm09 said:
Well, does your fastboot screen have that message?
If not, what does it say?
Click to expand...
Click to collapse
device is locked, status code 0
battery ok
.
.
.
.
,
fastboot reason: flash failure
all i tried was test to boot recovery, not flash,
fastboot boot rec.img

ok so i fastboot flashed stock recovery and it flashed fine and now im no more stuck in bootloader.
and that takes me to my second question/.....
1: can i fastboot flash stock recovery in the first place if im 100% stock, locked and non rooted on the latest kitkat ota
2: can i fastboot flash just the system.img like i flashed recovery and if that is possible hope towelroot will do the work????

Bricked? Please help!

My OPO is 100% stock currently running the second latest OTA update(coz I'd received a notification saying theres new update today but i haven't updated)
It was working perfectly fine until just now when I withdraw it from my pocket it shows the 1+ Powered by android loading screen.
I re-booted and it stuck at the same screen. I then boot into recovery and factory reset, wipe data wipe cache and boot and its still stucking at the same loading screen.
P/S : I was on wifi for a while in the cafe maybe it had downloaded the new OTA and maybe when the screen rubs against my pants in my pocket idk how it unlocks itself and it update itself with the downloaded(maybe) software update and eventually it dies. This might be one of the possibilities because if otherwise, it just dies itself without reason lel.
I've researched abit and someone suggested me to flash a stock rom using fastboot mode and PC adb command prompt which idk wtf is that lel. But in order to use that u need to unlock bootloader right, being 100% stock my bootloader is probably locked right?
omfg please guide me through this i need to solve this asap i dont have a backup phone. :silly::silly::silly::silly::silly::silly:

kingdew11 said:
My OPO is 100% stock currently running the second latest OTA update(coz I'd received a notification saying theres new update today but i haven't updated)
It was working perfectly fine until just now when I withdraw it from my pocket it shows the 1 Powered by android loading screen.
I re-booted and it stuck at the same screen. I then boot into recovery and factory reset, wipe data wipe cache and boot and its still stucking at the same loading screen.
P/S : I was on wifi for a while in the cafe maybe it had downloaded the new OTA and maybe when the screen rubs against my pants in my pocket idk how it unlocks itself and it update itself with the downloaded(maybe) software update and eventually it dies. This might be one of the possibilities because if otherwise, it just dies itself without reason lel.
I've researched abit and someone suggested me to flash a stock rom using fastboot mode and PC adb command prompt which idk wtf is that lel. But in order to use that u need to unlock bootloader right, being 100% stock my bootloader is probably locked right?
omfg please guide me through this i need to solve this asap i dont have a backup phone. :silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Follow this
http://forum.xda-developers.com/oneplus-one/help/solved-how-to-recover-oneplus-soft-t2864800
OR
Agai u can manually download any cm firmware
Then go to recovery
Factory reset
And flash desired firmware
FOLLOW this ( this is cm12 os)
http://webtrickz.com/guide-to-update-oneplus-one-to-cm12-lollipop-os/
If u don't like lollipop u can flash cm11s
FOLLOW this
http://www.technobuzz.net/update-oneplus-one-cm-11s-44s-resolve-several-bug-fixes/
note: u can find most guides on Google just search with keywords of your problems
Second mentioned flashing methods are most easiest prrocess
Factory reset and flash u r zip file

Problem solved. Detailed solutions for noobs like me!
OKAY here is what I DID. it may not work for u, but it worked for me. so if ur gonna follow these steps do it at ur own risk. and please dont expect me to helpp u to counter any special circumstances i.e. any condition not stated here coz im a perfect noob too, lel.
FYI this is called flashing roms in fastboot mode. And i had successfully flashed my OPO back into CM12.
STEPS :
Using a windows PC:
1) Download the UNIVERSAL ABD driver for Windows and freaking INSTALL IT.
2) Download the OnePlus One CM12 factory image “cm-12.0-YNG1TAS0YL-bacon-signed-fastboot.zip” (fastboot flashable package).
3) Download the flashing tools. ( it contains 4 things: adb.exe AdbWinApi.dll AdbUsbWinApi.dll and fastboot.exe)
the download links are available from this link:
ok im not allowed to attach links but u can search for it " webtrickz[dot]com how to flash cm12 factory image fastboot mode"
however, the steps given in the above link are crappy as well so follow mine =P just do the downloadings only from there.
4) Extract the 4 things from the flashing tools zip file into a folder, name it whatever****ing folder u want. we call it folder X.
5) and then extract all the things in the CM12 rom zip file into folder X.
6) Boot ur phone into fastboot mode simply by pressing and holding down the power button and the volume up button simultanoesly until u see "fastboot mode" with an Android face appears.
7) Connect ur phone to your PC with a USB cable. Now ur phone should be connected to the pc in fastboot mode.
8) open up folder X. then right click in folder X while holding down the Shift button, and click on "Open command window here"
p/s : this, I think, is like a special way to open up a cmd prompt used specifically for abd/fastboot. U can also actually open up cmd prompt normally but in order to do that you need to install idk some **** so that ur NORMAL cmd prompt will recognise abd or whatever **** it is. however, if u do that, u do not need to extract the CM12 rom files into folder X as the NORMAL cmd prompt will have the ability to, sorta like detect the CM12 ****s. anyways, forget it, just ****ing use the special way i.e. go to folder X , shift + right click to open up the SPECIAL cmd prompt)
9) a command prompt(cmd) should appear, Now check if u are connected by keying in "fastboot devices" in the cmd. Then the serial number of ur phone should turn up, and not " waiting for device" "devices not found" or any messages of that sort.
If the latter appears, idk how to help u sort that out urself lel.
10) Now u have to unlock the OEM in order for this flashing process to work. idk whats unlocking oem but just unlock it FFS. To do this, simply key in "fastbook oem unlock"
11) I think that under normal circumstances, a pop-up will appear in ur phone to let u choose if u really wanna unlock this oem thingy. BUT for me, my phone just rebooted back into the ****ing 1+ Powered by android screen idk why, but its alright i was on the right track as my oem has been unlocked. Then i powered off my phone and booted in back into fastboot mode once again. (FYI whenever I have to boot my phone to fastboot mode I disconnect the usb cable idk if this is necessary but thats what i DID)
12) go back to the CMD just now, and freaking paste the commands listed below into the CMD.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
13) Wait for several minutes, and when everything's done, the commands will stop at the last command which is "fastboot reboot"
Press Enter! and ur phone will reboot normally! =)

walpanmad said:
Follow this
http://forum.xda-developers.com/oneplus-one/help/solved-how-to-recover-oneplus-soft-t2864800
OR
Agai u can manually download any cm firmware
Then go to recovery
Factory reset
And flash desired firmware
FOLLOW this ( this is cm12 os)
http://webtrickz.com/guide-to-update-oneplus-one-to-cm12-lollipop-os/
If u don't like lollipop u can flash cm11s
FOLLOW this
http://www.technobuzz.net/update-oneplus-one-cm-11s-44s-resolve-several-bug-fixes/
note: u can find most guides on Google just search with keywords of your problems
Second mentioned flashing methods are most easiest prrocess
Factory reset and flash u r zip file
Click to expand...
Click to collapse
I can't flash it with recovery, as i cant 'insert' any ROM into my internal memory, as i cannot access my Internal memory, coz the phone wont boot?
However thank you so much! problem solved =)

kingdew11 said:
I can't flash it with recovery, as i cant 'insert' any ROM into my internal memory, as i cannot access my Internal memory, coz the phone wont boot?
However thank you so much! problem solved =)
Click to expand...
Click to collapse
Phone wont boot means?
If u are able to get in to recovery then its always possible to flash any official firmware without root with factory reset its easiest process to solve soft bricked device
First method mentioned is the same process u had done
(fastboot recover) but its automated process with OPO tollbox
Again fastboot method is usefull if u already enabled usb debugging in developer option before u went in to bootloop
I think u have previously enabled usb debugging
So it is also a method to recover u r problem
Any way its great news u got it worked

softbricked pixel

Hello everybody, hope u doing fine.
i was looking to root my pixel, so i installed kingroot and it rooted it just fine, then i wanted a root manager so i went to play store installed supersu (i guess that was the cause, i shouldn't have done that),then i opened it, it asked to download binaries(or install i'm not quite sure...), anyway this went fine too, then it sayed, everything gone right, restart your device, i clicked in reboot, it restarts with google logo and animations, but it bassicaly wont boot it is just stuck at the dots animation.
the problem is that i left oem bootloader locked, so now i can't do anything via fastboot adb... when i do: fastboot oem unlock , it says: failed (remote: oem unlock is not allowed)
i searched a bit more and found that we can unbrick qualcomm powered devices with qfil flashing tool, but requires a firmware wich is in .mbn format, wich i don't find on the internet (at least for the pixel), maybe there's a custom rom in mbn format...
i'm on android 7.1.2, stock rom, unlocked version.
please tell me if there's a way to fix that,
thank you in advance ? !

luigigigi said:
Hello everybody, hope u doing fine.
i was looking to root my pixel, so i installed kingroot and it rooted it just fine, then i wanted a root manager so i went to play store installed supersu (i guess that was the cause, i shouldn't have done that),then i opened it, it asked to download binaries(or install i'm not quite sure...), anyway this went fine too, then it sayed, everything gone right, restart your device, i clicked in reboot, it restarts with google logo and animations, but it bassicaly wont boot it is just stuck at the dots animation.
the problem is that i left oem bootloader locked, so now i can't do anything via fastboot adb... when i do: fastboot oem unlock , it says: failed (remote: oem unlock is not allowed)
i searched a bit more and found that we can unbrick qualcomm powered devices with qfil flashing tool, but requires a firmware wich is in .mbn format, wich i don't find on the internet (at least for the pixel), maybe there's a custom rom in mbn format...
i'm on android 7.1.2, stock rom, unlocked version.
please tell me if there's a way to fix that,
thank you in advance ? !
Click to expand...
Click to collapse
Did you try turning the phone off and then using the power-on + volume down key to get to the bootloader menu? from there press the volume up key until you get to recovery and the press the power button. In recovery do a factory reset. That should take care of stuff. In future, don't use kingroot as it's a malware ridden app (that is if you care about your personal data). If you need root then use Magisk instead. Gives you root and also a root manager. If you are planning to tamper with root then make sure to have your bootloader unlocked. Let me know if factory reset worked.

yes i tried to factory reset it from recovery mode ( i did that twice ) and that didn't help.

luigigigi said:
yes i tried to factory reset it from recovery mode ( i did that twice ) and that didn't help.
Click to expand...
Click to collapse
I have one more idea you could try. Download latest OTA update from here: https://developers.google.com/android/ota
go into recovery and follow the instructions given on the link I just gave you and apply the update using adb sideload in recovery. (You have to manually get into recovery as you did before but follow the instructions from the point where you're inside the recovery.) This should work. Seems that kingroot/supersu corrupted your system somehow. Let me know if it worked.

i already came across that site because i was on android p, i didn't like it so i went back to nougat...anyway to say that i have the nougat image .zip , so do i have to download the latest firmware ?

ok ok, that's not the same...SORRY ?? !!

luigigigi said:
ok ok, that's not the same...SORRY ?? !!
Click to expand...
Click to collapse
yeah, it's not the same and you'll find the 8.1.0 update there and the updates from the past. Give it a go and tell me the results when you're done

i tried that, everything went as intended, when i power it up there's animations of 8.1 but still wont boot.
i tried to wipe data and boot again, nothing.
is there a way to flash stock rom with adb (just like we did with that update) ?

now, the phone just booted up and i'm on the set up screen, BUT it showed me a pixel 2 , and theres a lock at the top left corner and it asked for a pattern (cause i did a wipe)... it's like another phone stuck in mine ?!

---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
[/COLOR]
luigigigi said:
now, the phone just booted up and i'm on the set up screen, BUT it showed me a pixel 2 , and theres a lock at the top left corner and it asked for a pattern (cause i did a wipe)... it's like another phone stuck in mine ?!
Click to expand...
Click to collapse
It's the newer setup screen. Have you managed to boot into system. Is everything working?

Arju said:
---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
[/COLOR]
It's the newer setup screen. Have you managed to boot into system. Is everything working?
Click to expand...
Click to collapse
no since i did a wipe ( i guess i shouldn't have done that) , now when it boots it is locked, it is asking for a pattern, wjch i don't know because i didn't set a pettern previously.
i guess i'm stuck here for ever ? ??

is there a way to flash the stock firmware via stock recovery or external flashing tools on pc, if yes please explain how !

((((Update))))
I didn't notice that there was a connect to Google option, so I finally set up the phone with my Google account and I'm back in.
I'm very thankful to you man you saved my phone, thank you a lot.
(Are you from India ? ? I love a lot India it's a beautiful place to visit and I really hope I could travel there once in my life, greatings from Algeria ?? )

luigigigi said:
(Are you from India ? ? I love a lot India it's a beautiful place to visit and I really hope I could travel there once in my life, greatings from Algeria ?? )
Click to expand...
Click to collapse
I'm glad it worked itself out.
I'm from Norway. Married a swede so living in Sweden now. My parents are from Sri Lanka (the island below India) but moved to Norway before I was born. I've been to Sri Lanka once. Would like to travel to India sometime too :silly:
Algeria seems nice. Must be hot there. I've never been to Africa. Would like to travel there too some day

Yes totally, Algeria is really safe and people here won't bother you (like if you're wondering how u would be seen or received as a foreigner) there's foreigner all year round but especially in summer time, just have something planned in advance because it's Algeria not USA or another well developed country ? but still there's a lot to see here, definitely worth the visit.
When it comes to whether, well it's a Mediterranean weather so expect nice warm days, that being said, there's some time when it goes rainy with thunders and cold, for example now it is very pleasant outside, but yesterday the weather gone crazy... I guess that's because of the global warming.

luigigigi said:
is there a way to flash the stock firmware via stock recovery or external flashing tools on pc, if yes please explain how !
Click to expand...
Click to collapse
1) Install the Google Android driver if your Pixel isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio....html#download
2) Download the factory system image for Pixel to C:/Google
https://developers.google.com/android/images
3) Unzip the system image folder into same folder, same with adb/fastboot tools in C:/Google
4) Run these commands in cmd prompt as administrator while Pixel is in bootloader mode
adb reboot-bootloader
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
hope this helps

MpandAUS said:
1) Install the Google Android driver if your Pixel isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio....html#download
2) Download the factory system image for Pixel to C:/Google
https://developers.google.com/android/images
3) Unzip the system image folder into same folder, same with adb/fastboot tools in C:/Google
4) Run these commands in cmd prompt as administrator while Pixel is in bootloader mode
adb reboot-bootloader
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
hope this helps
Click to expand...
Click to collapse
I'm sure this gonna help me in the future, as i'm planing to try some custom Rom's and i'm probably gonna brick it again so ? ... Thanks you ? !

erased os on mi mux 2s

Hi ppl. I need help bad! I accidentally erased my os. So when I try to flash a rom using the mi flash tool(which is amazing) it won't work because I have no operating system to enable USB debugging.so it says enable USB debugging but I can't. Any help would be appreciated TW RP installed unlock bootloader. Thanks in advance!!

just flash recovery rom using twrp then.

Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.

So twrp is flashed? Then yes try sideload. Also make sure your ADB is up to date as I've had that cause issues with large files and sideload before.
M.

dirtyrott3njb said:
Way ahead of you..I tried to transfer several times,files,etc from my PC for some reason two stops halfway and doesn't copy them or move them. Only thing I haven't tried it is ADB sideload.. for some reason that never seems to work for me or work out the way I wanted to.
Click to expand...
Click to collapse
Miflash doesn't need for usb debugging to flash rom I believe. It's all fastboot. If ur phone is not detected by pc, it means drivers.

It does indicate USB debuging not on. So yes it does . I've used it before to flash TWRP. The flash will also install the drivers before you use it so I can understand why it won't let me transfer anything from PC to phone when fastboot mode. It won't let me get past that stuff in this USB debugging is enabled. Frustrating brand new phone to only a couple weeks old.

Have you booted to twrp and format data (the one where you have to type "yes")?
Mi flash only required adb because it needs to run adb reboot fastboot. I'm in the States as well, PM me and maybe we can get this guy working over remote support. I haven't seen this issue myself, so I can't comment much.
Sent from my Mi MIX 2S using Tapatalk

@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?

dirtyrott3njb said:
@noobtoob,thx man. I can't format data because no keyboard is available for some reason. How can I pm you?
Click to expand...
Click to collapse
Its all good. I'm about to pick up my kids from school, so let me head home, I'll PM you in a bit. We can use TeamViewer or something. If it comes down to it, I also have my work login to use for remote assist. You just need a semi up to date laptop or desktop computer.
Hopefully we can get this solved quickly. I'm unfortunately not in your immediate area, otherwise much easier hands on. The company I work for is down the street from your location however, I'm just a remote systems guy.
Sent from my Mi MIX 2S using Tapatalk

How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?

dirtyrott3njb said:
How do u know where I'm at?? Ok sounds good. Where do I look for you msg at?
Click to expand...
Click to collapse
Tried to pm you but msg sent failed.

Only thing is for some reason I can't transfer anything for my PC to TW RP or my internal storage some reason just doesn't accept it and it's not my computer

I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.

sg01fc said:
I had the exact issue two days ago and the only thing that worked was to manually flash to stock. Since you already have the fastboot rom downloaded and extracted the hard work is done. What you need to do is to put all the files from that main folder (images) into a folder that you have adb installed. Then with your phone connected in fastboot open up a command prompt and once you have the directory set to where your fastboot is type the following and wait until each is done and says okay to move on.
fastboot flash modem modem.img
fastboot flash tz tz.img (I can't remember if this one actually flashed. I think it failed but it didn't matter)
fastboot flash logo logo.img
fastboot flash recovery recovery.img
fastboot flash system system.img (this one will take a long time to start flashing, don't worry. Also, there are about 5 files it will flash so be patient)
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
That puts you back to stock. I spent almost a whole night freaking out because I didn't have an OS and I couldn't get TWRP to reinstall. Once I did that and got things going I downloaded the same versions update on the phone (the one that can be flashed through the update page in settings) and did a flash of that as well.
Click to expand...
Click to collapse
The OP's issue was solved by just flashing TWRP, booting to it and sideloading the Stock ROM. I had the OP download the fastboot files as well, but we ended up not needing them.