Related
I bought a Motorola XT925 on ebay branded Orange France and loaded with Jelly Bean 4.1.1 firmware.
The phone was sold to me as a 4G/LTE capable device. Not seeing an option for 4G/LTE in the phones menu, I then dug around the Orange France web portal. There it says the phone is not 4G/LTE compatible. This was confirmed by Motorola France.
So my big question: is the radio hardware in this Orange France phone the same as an XT925 that I would by from Rogers Canada, but just not initialized for 4G/LTE? Or is the actual Radio hardware different? Even Motorola France was not able to tell me over the phone about the exact hardware.
Do I have a hope to get 4G/LTE working on this phone?
I want to try a Rogers firmware on this phone, but don't want a 200,00$ paperweight.
Thanks for reading.
is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.
hbenz2008 said:
is the bootloader unlocked? check by booting into apfast mode. Moto website can unlock your BL if needed, after that you can test any firmware and flah any radio of course with caution .There is hope.
Click to expand...
Click to collapse
I have a custom recovery utility installed after rooting and unlocking the bootloader and just completed a backup on the phone. I figure since the phone is wearing jelly bean 4.1.1 I ought to be able to take the Rogers firmware jellybean 4.1.2 and flash that onto the phone. Just not sure how to make sure that the modem gets flashed when I do fastboot flash system system.img. So I am looking around to piece together the instructions on how to flash the modem or does the system image contain all I need for the modem and all else?
I kinda like the lock screen on the Orange.fr firmware -- has a sliding mute feature that might not stick around after a system flash. minor detail though as all I really want is a working LTE device.
Thanks
Rsd lite 6.1 to flash
hbenz2008 said:
Rsd lite 6.1 to flash
Click to expand...
Click to collapse
RSD Lite is a windows utility and at the present time I do not have a windows computer. I have unlocked the bootloader and flashed the recovery successfully with mfastboot for linux. So that;s where I am at. ( I find it ironic that a phone OS based oin linux should be largely dependent on a non-linux OS. Strange but true.
@hbenz2008 tell me about flashing the modem so that I can have LTE/4G access. What do I need to do?
excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.
hbenz2008 said:
excellent man, did you update to kitkat yet? you are free to try firmware from any carrier now. Look here for some Jelly Bean downloads to try:
http://sbf.droid-developers.org/phone.php?device=6
Then there are many ways to get on kitkat if you wish.
Click to expand...
Click to collapse
I have downloaded the 4.1.2 Rogers firmware but to be honest I don't know exactly what or how to do with the zip file. I've opened the archive -- I even flashed the modem and all the rest of the blobs onto the phone, one by one based on a batch file from another archive. What happened was I lost my patience waiting for the phone to reboot as it appeared to be stuck on the Motorola boot logo. (Maybe it was rebuilding the cache??) I used the recovery to get the phone back. So if you can give me a clue as to what to do exactly with the firmware zip -- much appreciate your council.
i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918
hbenz2008 said:
i dont have a mac but i will try to get you some instructions. Under windows, we just rsd the xml file after extracting the firmware. This may help
http://forum.xda-developers.com/showthread.php?t=1165672
http://forum.xda-developers.com/showthread.php?t=994918
Click to expand...
Click to collapse
I dug up an old netbook with xp on it and managed to use RDSlite it to flash the Rogers firmware and voila! Full service phone. except for one tiny snag. Earlier I had installed a custom recovery utility cwm6.2.2.8-XT925(epinter) and it worked. Now though the cwm recovery util got wiped and my subsequent attempts to re-install fail. I speak: "linux-fastboot flash recovery cwm.img. response: Max 30M sending recovery.
Weird it never progresses or finishes. Beginning to think I have the syntax wrong.
Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd
hbenz2008 said:
Try mfasboot
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Fastboot flash recovery recovery.img is the right cmd
Click to expand...
Click to collapse
Thats what I have as a linux version (mfastboot). Got it from a link posted by @ATTACK and it worked properly before I flashed 4.1.2 today. I'll work on it at least now I have a phone that works and shows the options I was sold. Just wondering if RSDLite does something crippling when it writes the flash to the phone.
Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.
hbenz2008 said:
Rsd is clean. You can always try other recoveries. Cmw6.0.4.4 if I remember correctly works
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
And twrp 6.0.
Click to expand...
Click to collapse
So something does seem to have changed. I no longer have permission to erase with the mfastboot utility. And I am refering to permission on the device not in my local shell. I sudo to the shell locally then run fastboot which returns the following:
gryphon platform-tools # fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.034s
gryphon platform-tools
the device status code is 3 and unlocked so I am baffled.
i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.
hbenz2008 said:
i have fought that error before but dont recall what solved it. Either another recovery or flashing with fastboot, or mfastboot.
Click to expand...
Click to collapse
If you think of another possible solution let me know. As of now no fastboot utility works on my phone now.
At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.
hbenz2008 said:
At one point I also downloaded android sdk from Google and used fastboot tools/platform to flash things up.
Click to expand...
Click to collapse
I have the android-sdk installed and the fastboot included is known to cause problems with image files that are large. Thats where mfastboot comes in handy.
Now everytime I powercycle the phone fastboot appears on the screen and shows a failed flash notice. I'd like to clear up this issue pronto. what a pain . An adventurous pain
Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones
while you at it man, can you please grab "gps.conf " from system/etc and post here .It is about 2kb size. Merci
hbenz2008 said:
Maybe flash a different recovery with it hopefully overwrite what's in the phone. If not, flashing 4.1.2 with rsd and a fresh recover maybe an easier way. Even European 4.1.2 rtfr modified to get kk update. There is a thread:make your xt 925 updatable. Check it out, you may kill two birds with 5 stones
Click to expand...
Click to collapse
Good news! I got the fastboot flash failure flag cleared away and cwm recovery reinstalled. Still can't flash anything with fastboot of any stripe and I am betting this is because the image files in the sbf archive are signed. My phone is now vritualy identical to any Fido branded phone, complete with a Fido boot logo. Cute.
There ought to be a way to overwrite signed images, besides waiting for a new firmware release. The bootloader is unlocked and phone rooted yet fastboot flashing is not currently possible.
How can I unlock the signed images on my phone?
BTW heres my gps.conf. Whats your interest in this file?
Code:
#Test
#NTP_SERVER=time.gpsonextra.net
#Asia
# NTP_SERVER=asia.pool.ntp.org
#Europe
# NTP_SERVER=europe.pool.ntp.org
#North America
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra2.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra2.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra2.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL = 2
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# supl version 1.0
SUPL_VER=0x10000
WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.
This is the stock recovery version, correct?
koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.
TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones
koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.
Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )
kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!
It works in LOCKED BOOTLOADER??? .-.
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.
TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
lazarus2297 said:
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
Click to expand...
Click to collapse
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
razrlover said:
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Click to expand...
Click to collapse
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
foosion said:
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
Click to expand...
Click to collapse
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
phonefreedom said:
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
Click to expand...
Click to collapse
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
lazarus2297 said:
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
Click to expand...
Click to collapse
+Natahranta had shared the following with me and I hope it helps in your case...
"Download factory image from Google, unpack it, insidebis another zip, there is boot.img file
Flash it to both slots A and B. It must be the same version/update your phone was on.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
If you're not sure which exactly stock rom build your phone is on, use the flash_all.bat to flash the whole image on your phone, to be sure you have no mismatch between system and boot. Just remove "-w" from the bat file so it doesn't erase your user data"
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
lazarus2297 said:
I have relocked the BL then booted into the OS
Click to expand...
Click to collapse
I don't have any suggestions for your issue. But don't relock it, ever. You are playing with fire, if it goes bad and it's locked you are done.
lazarus2297 said:
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
Click to expand...
Click to collapse
I had this problem and created a thread about it a month ago: https://forum.xda-developers.com/pixel-2/help/failed-remote-command-flash-error-t3701929. A couple other people in that thread are now also reporting the problem.
No one seemed to know what the " FAILED (remote: Command Flash Error)" means. I never figured it out.
At the time of the November update, however, I was able to sideload OTA images with adb without problem. I assume that the OTA method also updates the bootloader, like the Dev Preview did for you. I couldn't tell with the November update, though, because it had the same version of the bootloader in it as the one that shipped with the phone.
So I'm wondering if simply sideloading the current December OTA image with adb would accomplish the same thing you did, without having to lock the bootloader, unlock it again, and go through the pain of wiping the device. I wonder if there was just something weird about the original version of the bootloader. Weirdness like this was discussed early on with the Pixel 2 in this XDA article: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/ If I'm right, then once one sideloads the December OTA image and gets a new bootloader, there may not be an issue flashing bootloaders with fastboot in the future. I assume that the Dev Preview also used the OTA method to update the device.
In other words, I'm wondering if the step of unlocking and relocking the bootloader was not necessary. You just had to do it to get the Developer Preview (right?).
Just guessing here. I haven't had time yet to try this.
Okay, I tried my idea above and I was correct. Simplying sideloading the December OTA image updates the bootloader. After that the problem is solved. I can successfully flash the bootloader .img file directly (from the factory image zip) using fastboot. So I assume going forward there should not be any problems flashing factory images, instead of sideloading OTA images.
This solution also avoids having to lock and unlock the bootloader and wipe the whole device in the process.
cb474 said:
Simplying sideloading the December OTA image updates the bootloader.
Click to expand...
Click to collapse
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
-----------
Nevermind. I figured out that recovery is part of boot now. I flashed the factory boot and flashing OTA now.
snovvman said:
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
Click to expand...
Click to collapse
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
cb474 said:
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
Click to expand...
Click to collapse
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
snovvman said:
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
Click to expand...
Click to collapse
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php
kendong2 said:
https://forum.xda-developers.com/showpost.php
Click to expand...
Click to collapse
That link leads to nothing.
---------- Post added at 01:13 AM ---------- Previous post was at 01:11 AM ----------
snovvman said:
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
Click to expand...
Click to collapse
Yeah, I saw that. I'm just hoping with what was learned from the original Pixel and given that supposedly most phones will eventually use the A/B partition scheme that maybe TWRP will advance further on the Pixel 2. I really miss nandroid backups. I miss LineageOS too. Everything was so much simpler on my old Nexus 4. And I wasn't constantly feeling like I was going to brick my device every time I tried to do something.
cb474 said:
That link leads to nothing.
Click to expand...
Click to collapse
Sorry, did that on the phone. Was supposed to go here: https://forum.xda-developers.com/showpost.php?p=74704694&postcount=155
TWRP 3.2.0.0 final release (as I understand it) has been announced a few days ago. Don't know why the thread title still says beta.
This is freaking weird. Anyway, followed post #11 to sideload DEC OTA zip in stock recovery, and now finally I have a bootloader that is 0066 on both slot a and b. Thanked @cb474 !
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
Currently I have all patches after 4.88 base so may to october security patch...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
and Magisk(v17.2) prerooted patched myself here:
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
Mirror: (All Images)
https://mega.nz/#F!QQp1jQQZ!k5ejlU2NJyic0HusCa_IAQ
Nice job, i have been waiting for this for a long time. Thank you so much ??.
Trissi said:
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
Magisk Prepatched Images will be added later...
Click to expand...
Click to collapse
Thanks sir
Greatttttt
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Mo4o293 said:
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Click to expand...
Click to collapse
Thats weird... what model do you have? , I thought they work on all Models...
On my device (TA-1012)[Single sim 128gb/6gb], I have exactly the same patches on a and b and both work like a charm with their specific images... Just redownloaded and tested it again...
To narrow down your problem further:
Did you flash anything else? Is your device booting normally when just rebooting? Root? Twrp?
Mo4o293 said:
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Click to expand...
Click to collapse
If you have another model and some time leftover I would greatly appreciate if you(and everyone else reading this with Another model):
1. could reflash the 4.88 Stock Image
2. Turn off automatic update
3.follow this Upgrade guide over and over again
https://forum.xda-developers.com/no...root-nokia-8-ability-to-t3848390/post77751877
4. Afterwards send me the stock_boot_(randomstuff).gz Magisk generates as Backups in the folder /data or (only viewable with root explorer) AND a screensho of the file creation dates so I know which is which...
I would then upload them and add them to the thread to help others with your model...
No worry's if you don't have time...
Trissi said:
Thats weird... what model do you have? , I thought they work on all Models...
On my device (TA-1012)[Single sim 128gb/6gb], I have exactly the same patches on a and b and both work like a charm with their specific images... Just redownloaded and tested it again...
To narrow down your problem further:
Did you flash anything else? Is your device booting normally when just rebooting? Root? Twrp?
Click to expand...
Click to collapse
Thanks for the replay! My device is TA-1012 [4/64]. I haven't flashed anything. I neither have TWRP or root. When rebooting it is showing the warning that my bootloader is unlocked (offical method). But i noticed something strange. Maybe you will laugh at me :laugh: but the thing is when i boot the phone and the warning pops up it says to press the power button to continue but that doesn't work. I have to wait to boot itself. In the other hand when i boot the stock images you provided the power button works and when i press it, the warning disappears and the android logo pops up. I dont know if this was helpful in some way but i wanted to mention it. Also i will post the backed up img soon that you wanted up there.
Ok so i came up with another idea. I forgot to mention that all these steps i did on Linux so i have Windows also and switched to see if the things are the same. When i enter in cmd, adb recognizes the device without problem. When i write adb reboot bootloader everything is fine. BUT when i write fastboot devices when my phone is in download mode , nothing happens. When i try something like fastboot reboot or fastboot boot xyz.img it says <Waiting for device>. I tried adb and fastboot installer but again nothing. I cannot find nokia drivers, but in OST LA there are 3, i installed them and again nothing. So what should i do?
Edit: It worked when i downloaded new version of adb and fastboot CLI but again - booting the oct img even in Windows cmd makes the phone stuck on android logo
Mo4o293 said:
Thanks for the replay! My device is TA-1012 [4/64]. I haven't flashed anything. I neither have TWRP or root. When rebooting it is showing the warning that my bootloader is unlocked (offical method). But i noticed something strange. Maybe you will laugh at me :laugh: but the thing is when i boot the phone and the warning pops up it says to press the power button to continue but that doesn't work. I have to wait to boot itself. In the other hand when i boot the stock images you provided the power button works and when i press it, the warning disappears and the android logo pops up. I dont know if this was helpful in some way but i wanted to mention it. Also i will post the backed up img soon that you wanted up there.
Click to expand...
Click to collapse
The Power Button stuff is exactly the same for me... Don't think thats the issue...
Really weird, would love to debug further but really have not much other ideas...
Did you try newest fastboot/adb binaries on windows too?
Do you have access to another pc to try it on?
Switched out cables/ports used?
Trissi said:
The Power Button stuff is exactly the same for me... Don't think thats the issue...
Really weird, would love to debug further but really have not much other ideas...
Did you try newest fastboot/adb binaries on windows too?
Do you have access to another pc to try it on?
Switched out cables/ports used?
Click to expand...
Click to collapse
I've switched ports, tried another pc even with different OS (win7). Downloaded the newest adb and fastboot binaries from Android Developers site - nothing. Also i ran a test in fastboot and its says:
bootloader unlocked: true
critical unlocked: false. But i dont think critical is necessary, isnt it?
Mo4o293 said:
I've switched ports, tried another pc even with different OS (win7). Downloaded the newest adb and fastboot binaries from Android Developers site - nothing. Also i ran a test in fastboot and its says:
bootloader unlocked: true
critical unlocked: false. But i dont think critical is necessary, isnt it?
Click to expand...
Click to collapse
If critical was never unlocked it can't have been modified(I think)
Really outta ideas here sorry mate...
Have you tryed booting the prerooted imgs?
Trissi said:
If critical was never unlocked it can't have been modified(I think)
Really outta ideas here sorry mate...
Have you tryed booting the prerooted imgs?
Click to expand...
Click to collapse
Yep the same thing
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
I think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
I have similar issues. I have ta-1012 4/64. When it was of september patch, no september image worked (modified or not), it stucks at "android powered" logo. This is the volatile booting which is performed by "fastboot boot" command.
I use a linux desktop. I tried the latest fastboot executable which came with android-studio and also the one on archlinux android-tools package. (they are a bit different) Results are same.
Now it has october patch. No success with october boot images, too
---------- Post added at 21:59 ---------- Previous post was at 21:53 ----------
Mo4o293 said:
Yep the same thing
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
I think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
Click to expand...
Click to collapse
I think you should wait for TWRP.
Dr. Slump said:
I have similar issues. I have ta-1012 4/64. When it was of september patch, no september image worked (modified or not), it stucks at "android powered" logo. This is the volatile booting which is performed by "fastboot boot" command.
I use a linux desktop. I tried the latest fastboot executable which came with android-studio and also the one on archlinux android-tools package. (they are a bit different) Results are same.
Now it has october patch. No success with october boot images, too
---------- Post added at 21:59 ---------- Previous post was at 21:53 ----------
I think you should wait for TWRP.
Click to expand...
Click to collapse
Yep. We are the black sheeps. Anyway i will definitely wait for TWRP because the other things are risky and thats my daily driver. BTW Im on Manjaro which is based on Arch.
Mo4o293 said:
think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
.
Click to expand...
Click to collapse
If you do happen to do that please remember this if you have Time....
If you have another model and some time leftover I would greatly appreciate if you(and everyone else reading this with Another model):
1. could reflash the 4.88 Stock Image
2. Turn off automatic update
3.follow this Upgrade guide over and over again
https://forum.xda-developers.com/no...root-nokia-8-ability-to-t3848390/post77751877
4. Afterwards send me the stock_boot_(randomstuff).gz Magisk generates as Backups in the folder /data or (only viewable with root explorer) AND a screensho of the file creation dates so I know which is which...
Click to expand...
Click to collapse
Trissi said:
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
Currently I have all patches after 4.88 base so may to october security patch...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
and Magisk(v17.2) prerooted patched myself here:
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
Click to expand...
Click to collapse
You can download it on GoogleDrive? links do not open
Anatoly64RUS said:
You can download it on GoogleDrive? links do not open
Click to expand...
Click to collapse
Problem seems on your side
Anatoly64RUS said:
You can download it on GoogleDrive? links do not open
Click to expand...
Click to collapse
Works fine for me too...
I have A pretty restrictive https configuration on that server...
Do you use A massively outdated browser? If Not it should work...
Trissi said:
Works fine for me too...
I have A pretty restrictive https configuration on that server...
Do you use A massively outdated browser? If Not it should work...
Click to expand...
Click to collapse
Browsers are all updated, I'm just from Russia, so a big request to anyone is easy, upload to google drive
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
Did you ever get any help? I am in the same boat.
ConsoleHax said:
Hi guys,
I made a mistake installing the Android 11 firmware update and afterwards flashing TWRP and installing Magisk.
Second mistake because I couldn't boot I flashed an old Fastboot ROM, but that doesn't help me.
Can anyone please point me to the fastboot rom for android 11 update?
Thank you very much.
Click to expand...
Click to collapse
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
Piricho said:
Did you ever get any help? I am in the same boat.
Click to expand...
Click to collapse
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
RokCruz said:
I guess the best way to go back to stock is using msmtool you can find it here: with android 10 for international and European version: Thread '[OP7PRO][LATEST OOS 10.3.8 GM21AA | OOS 10.0.10 GM21BA] Collection of unbrick tools' https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
saurabh_op7 said:
Hey,
I bricked my OP7 after what seemed like successfully installing and using Android 11. I am getting the Teamwin blinking brick.
This(
) seems like something I can do- flashing Fastboot ROM(even though I'll lose data, but wth). Can you please tell me if this comment of yours applies in my case- i.e. is the link you are suggesting for Android 11 Fastboot ROM valid?
Click to expand...
Click to collapse
Just flash stock boot.img
RokCruz said:
Just flash stock boot.img
Click to expand...
Click to collapse
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
saurabh_op7 said:
As a rain check, as I am new to this, and don't want to screw up more,
You mean I can use this method-
Restore OnePlus 7/7T/7T Pro to Stock via Fastboot Commands - DroidWin
to flash the latest stable build on OnePlus support, i.e. this-
https://otafsg1.h2os.com/patch/amaz....P.35_OTA_0350_all_2103221240_3e944b9d067.zip(OnePlus7Oxygen_14.P.32_OTA_032_all_2101280019_b2a62765ba0c485e.zip)
??
Or do you suggest to use the Android 11 firmware available on XDA?
Click to expand...
Click to collapse
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
RokCruz said:
If you ended with a blinking TWRP just flash the stock/rooted boot.img if you are using stable you can obtain it here(Post in thread 'Android 11 Release - Finally!' https://forum.xda-developers.com/t/android-11-release-finally.4251267/post-84717089)
Or if you are on a Open Beta here: Thread 'OxygenOS Android 11 Betas (OnePlus 7 Pro) released (Open Beta 4 now available)' https://forum.xda-developers.com/t/...o-released-open-beta-4-now-available.4221067/
Click to expand...
Click to collapse
RokCruz said:
You can do it with the fastboot zip but you need to download all the firmware, in some threads you will find the stock/rooted boot.img from stable and OB, I shared both in this message
Click to expand...
Click to collapse
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
saurabh_op7 said:
I am pretty sure I know my OS, but is there a way to find out?
I was running the stable, but flashing stock boot just led me to a boot loop with the Original Recovery, it's giving me options to
1. Wipe data and cache
2. Reboot to fastboot
3. Reboot to recovery
The fastboot flash commands above to flash stock OS didn't work, due to one error or another.
Anyhow, I had read somewhere fastboot continue works(here: it wasn't working before for me), so I tried that again, and now I am just stuck on 1+ Fastboot screen. I will wait it out to see if it boots into system.
Otherwise, I am thinking I reload fastboot and flash stock boot just like I did- and from there wipe data, but what do I expect then??
The way I see it, I am just stuck in some serious boot issue, and might eventually have to go down the path of msndownloadtool, any suggestion?
Click to expand...
Click to collapse
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
RokCruz said:
Flashing the stock boot.img should be enough to boot into system without problems because TWRP can't decrypt data in android 11.
In this point you can try a factory reset from stock recovery this will keep device files but will erase all your config and apps
To figure out what version of firmware you had you can run this command in fastboot
Fastboot getvar all
Click to expand...
Click to collapse
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
saurabh_op7 said:
Flashing didn't work to boot into system, I was just getting stuck in the Recovery boot loop, it finally booted into system once I wiped my data(files, music, etc -option);
I did try factory reset, only once I cleared the partition, did the boot loop give way to boot into system;
It booted back to Android 11, but it's all glitchy: Boot taking too long, WiFi not switching on, Call not working, Data is working though- basically it's very screwed up, got a couple of errors too- it's like watching an amnesiac old person.. if you get the gist.
So, now I am considering a stable build from Oneplus support website as a local upgrade and booting back to that..
I am hard pressed for options, let me know if you think something else works better, thanks!
Click to expand...
Click to collapse
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
RokCruz said:
I guess msmtool it's the best way to restore your phone, remember that msmtool will re-lock your bootloader so if you want root you need to unlock your bootloader again.
Use msmtool and instructions form Here(there's an android 9 and android 10 for Global and Europe versions, use android 10)
Click to expand...
Click to collapse
My model is GM1901, in support intro for the link you provided, that's not included?
saurabh_op7 said:
My model is GM1901, in support intro for the link you provided, that's not included?
Click to expand...
Click to collapse
Wait GM1901 is a OnePlus 7(non pro) right?
RokCruz said:
Wait GM1901 is a OnePlus 7(non pro) right?
Click to expand...
Click to collapse
Yeah.. ?
saurabh_op7 said:
Yeah.. ?
Click to expand...
Click to collapse
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from HereI
Click to expand...
Click to collapse
Yeah man, I realised.. anyway, I flashed the boot image from Xda for OP7.. nevertheless, mom tool it is.. thanks..!
RokCruz said:
This is the OnePlus 7 pro forum so, I assume you was a 7 pro user, now all makes sense you don't flash the correct boot.img for your device so all woes wrong.
You need to use msmtool from Here
Click to expand...
Click to collapse
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Update: I have been roaming around the corridors of this forum since about a week now. Thanks @RokCruz !!
Finally, used msm tool, although I suspect I still had the option of flashing TWRP and Magisk as I had access to phone and fastboot, but the system was super glitchy.
saurabh_op7 said:
Hey, I am on Mac, I see that Msm is windows-specific.. any way out?
Click to expand...
Click to collapse
I guess that the only way is using the fastboot ROM
RokCruz said:
I guess that the only way is using the fastboot ROM
Click to expand...
Click to collapse
Any idea if we're gonna get one soon?