Database Users

[Q] [Fastboot] Can't flash Stock ROM

Hello there!
I have a Nexus 7 Device, I rooted it using a toolkit, everything was working great, then I messed up a little and I need to restore it using a Factory Image (a.k.a Stock ROM)...
The problem is, when I try to flash the .zip, it gives me the following error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to some tutorials, you type the following commands to flash a ROM:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update ROM.zip
Click to expand...
Click to collapse
Because I'm afraid of something going wrong, I didn't erased any partition, so if for some reason the flashing procedure stops, I have the old data/partitions working because I didn't erased any, I just used the following command:
fastboot -w update ROM.zip
Click to expand...
Click to collapse
So, the questions are:
Do I need to erase the partitions first before trying to flash the Stock ROM?
Should I try flash each .img separately?
Additional Information:
Android is working, I'm able to boot with success.
Bootloader unlocked.
I didn't flashed any custom Bootloader/Recovery/ROM, everything is from Factory/Stock.
I have tested flashing the ROM under Windows and Linux (Ubuntu), it gives me the exact error.
The .zip I'm using isn't corrupted. (And it's directly from developers.google.com)
If flashing without erasing the partitions worked, I would erase them (To delete ALL data/trash) and flash it again...
P.S: First post!

I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD

korockinout13 said:
I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Hello!
Thanks for the answer, I tried to flash system.img and it worked, fastboot automatically erases the system partition.
I have now a clean system, thanks!
For other people with the same problem as me:
1 - Enter Fastboot Mode
2 - Extract system.img
3 - Run "fastboot flash system system.img"
4 - Enter Recovery Mode and do a "Factory Reset" (Optional, I guess)
5 - Enjoy!

Spenzert said:
fastboot automatically erases the system partition.
Click to expand...
Click to collapse
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers

bftb0 said:
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers
Click to expand...
Click to collapse
I believe fastboot really erased the partition, there's no "SuperSU" anymore and I have attached a screenshot of fastboot erasing the partition.
Cheers!

I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?

bftb0 said:
I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?
Click to expand...
Click to collapse
Android SDK Manager says "Rev. 16.0.1" (Platform-tools), maybe fastboot erased the partition first because I used "fastboot flash" instead of "fastboot update"...
A little off-topic:
I tried to root manually my Nexus and it's really easy, I might make an updated tutorial soon on how to root it manually
Have a good day!
Edit: I tried to flash TWRP (Recovery) and it didn't erased the partition first.

[GUIDE][HOW-TO] Update your bootloader

XT1063 - XT1064 - XT1068 - XT1069
Disclaimer
Code:
Your warranty is (probably) not void since these
are the official images. Backup, always!!!
I am not responsible for bricked devices, dead SD cards,
you getting fired because the alarm app failed,
thermonuclear war, or anything else.
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device,
I will laugh at you. Hard. A lot.
New version 10/10/16
Get your Model number by opening back cover and looking at the sticker
Download the correct folder for your device: Google Drive | Mega
Shutdown your Phone
Boot into bootloader ( Hold volume - and power for 5 seconds and then release)
Connect phone to a pc with fastboot installed
Open a cmd / terminal window
Change the directory to the one where you saved the device specific files you downloaded
Type/copy
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Hit the Thanks! button (right bottom corner of this post)
Please read Q&A before asking a question
Thanks: luca020400 and LuK1337 and skaveelicious

Q & A
Q: Could you make a video because I don't understand the guide?
A: No, there won't be a video because if you don't understand the guide you will most likely harm your device.
Q: Can I flash kk roms on lp bootloader?
A: Yes, but the other way around only works with stock (based) roms.
Q: Do I need to unlock the bootloader?
A: No, if you only update the bootloader you don't need to unlock, if you want twrp or such a thing this is required.
Q: I have no signal, how to fix it?
A: http://forum.xda-developers.com/showpost.php?p=60740579&postcount=183
Q: I have a XT1063 and no signal, how do I restore it?
A: Use these files: https://mega.co.nz/#!QFonVR4J!dhNw1kwj9GBc5vh14s-SLw3VeCa34IboIQlAZ13Fjq8
Q: My bootloader is 4882 or higher do I need to update?
A: No, this guide makes your bootloader 4882, ( downgrading is impossible ) so you are good
Q: I got success every time, but I am still on the old bootloader, what went wrong?
A: You need admin rights for these commands since fastboot otherwise won't recognize the device with correct permissions. On windows run cmd as admin, on linux use sudo in front of all lines.
Q: Something is not working, were do I find my country specific files?
A: This has all official firmware, you can find the right one for you and use the files from that zip. Sadly the server is very slow. Now faster mirror

gregor160300 said:
Mine for Q & A if any
Click to expand...
Click to collapse
AFH files are up

As I've said here, be cautious when doing this to a brazilian XT1068 (not sure if it's the same for XT1069).

Does updating to official UK lp ota with locked boot loader automatically update it to lp once unlocked or do I still need to run this?

daviss101 said:
Does updating to official UK lp ota with locked boot loader automatically update it to lp once unlocked or do I still need to run this?
Click to expand...
Click to collapse
If you have bootloader from december then it is updated already.

Thanks
Sent from my Moto G 2014

Thanks for your work i have done all the steps but it wont work for me.........

luca020400 said:
AFH files are up
Click to expand...
Click to collapse
Thanks! I am not going to hit the button

Sosa88 said:
Thanks for your work i have done all the steps but it wont work for me.........
Click to expand...
Click to collapse
Can you please be more specific in what doesnt work and what the error is so I can help you

@gregor160300 i think it's not Bootloader related.... because i can flash ACIP without error.
But when i try to flash PAC or the latest CM nightly there comes "Error updater binary in zip"...... I'm using the latest twrp.

Sosa88 said:
@gregor160300 i think it's not Bootloader related.... because i can flash ACIP without error.
But when i try to flash PAC or the latest CM nightly there comes "Error updater binary in zip"...... I'm using the latest twrp.
Click to expand...
Click to collapse
For as far as I know it is indeed not bootloader related, I had the same error on my old device and still dont know how to fix it, sorry.

Sosa88 said:
@gregor160300 i think it's not Bootloader related.... because i can flash ACIP without error.
But when i try to flash PAC or the latest CM nightly there comes "Error updater binary in zip"...... I'm using the latest twrp.
Click to expand...
Click to collapse
gregor160300 said:
For as far as I know it is indeed not bootloader related, I had the same error on my old device and still dont know how to fix it, sorry.
Click to expand...
Click to collapse
Yes , this is due boot loader.
Gregor open the updater-script ( cm & pac ) and you will find why

Bootloader
luca020400 said:
Yes , this is due boot loader.
Gregor open the updater-script ( cm & pac ) and you will find why
Click to expand...
Click to collapse
Now I found the line I think: assert(getprop("ro.bootloader") == "0x4882" || abort("This package supports bootloader(s): 0x4882; this device has bootloader " + getprop("ro.bootloader") + "."); don't know how to fix it but you might want to try one of the stock recovery tools with your correct firmware and then install twrp again.

gregor160300 said:
Now I found the line I think: assert(getprop("ro.bootloader") == "0x4882" || abort("This package supports bootloader(s): 0x4882; this device has bootloader " + getprop("ro.bootloader") + "."); don't know how to fix it but you might want to try one of the stock recovery tools with your correct firmware and then install twrp again.
Click to expand...
Click to collapse
Fix --> Update bootloader

@luca020400 i think that my phone is on the latest Bootloader......
Tell how can i upgrade that fu** Bootloader ?

Sosa88 said:
@luca020400 i think that my phone is on the latest Bootloader......
Tell how can i upgrade that fu** Bootloader
Click to expand...
Click to collapse
Pc with adb installed
adb shell "getprop ro.bootloader"
Tell me the output

allowed me to flash CM12 nightlies!!
Thank you very much!
Updating xt1064 bootloader finally allowed me to flash cm12 nightlies.
I had been getting binary update error in TWRP.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@luca020400 thats it...

Sosa88 said:
@luca020400 thats it...
Click to expand...
Click to collapse
You should be able to flash cm12 :/
Reflash recovery

Turbo Unbrick for Android 4.4.4 - 5.1

There are a few types state of brick of the phone. Let's review two of them:
1. “Softbrick” - the state when the system is not booting, but the PC recognizes the phone as “ADB Device” and the phone can boot to bootloader mode. This state is like a baby's runny nose and can be healed by the simple reflash using RSDLite (the tool avaliable for everybody), or by reflashing the parts of firmware via fastboot.
2. 'Hardbrick' - the hard case that needs a lot of work and knowledge. Sometimes hardware intervention needed in order to fix the phone (test-point contacts closure, battery disconnection, etc). Sometimes the phone could not be repaired without motherboard replacement.
We'll review the phone recovery after the second type of bricking.
The phone in “hardbrick” state is recognized by PC as:
- “Unknown device”. In this case you need to install the Qualcomm USB drivers on PC by hands from the attached file "Qualcomm_USB_Drivers.7z" (download it and unpack to any path you want). The phone will be recognized by PC as “Qualcomm HS-USB Diagnostics 9008” device after the driver's installation. Sometimes it is needed to disconnect the phone and to hold the power button during 20-30 seconds to recognize the phone.
- “Qualcomm HS-USB Diagnostics 9008” (nothing happens when you press the buttons on the phone). No needed installation driver's in this case.
The PC will see your phone as shown on picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then the wonderful utility “TURBO-UNBRICK” comes to the rescue. This is a small program but it makes a great job.
Unpack the archive that includes the utility, connect the phone to PC and run “go” file. And you will observe that your brick will become alive! You will see the next picture at your revived phone's screen:
It's almost a win but you need to make some more actions.
Put the files gpt.bin, radio.img, bootloader.img (also attached), to the “C:\adb” folder on your PC and run the next commands in the command line:
Code:
fastboot flash partition gpt.bin
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
fastboot reboot
Now you can enjoy! Your friend is alive and greets you by its bootanimation. In that case when you've broken the firmware and the phone is not booting after the bootanimation, you need reboot in bootloader and reflash the firmware by RSDLite.
Android 4.4.4
Link to download the attached files
https://drive.google.com/open?id=0B-o0d4PkVUwBflNNbF96UWx1N1JtVkY5S1JrM25lemIxVFgtTEdwb0lEUmxqYzlqc2VfZzg&authuser=0
Android 5.1
Link to download the attached files
https://drive.google.com/open?id=0B...l3YThKNE5iWkw3eVgtNzl5aXQwTTdCNElBVTd5VWc5V3c

Thanks bud, I wasn't able to register with my gmail account.

Turbo unbrick
Wish I had this a month ago,had to send my phone off to be jtagged.I'm sure I'll need it again.Thank you for your work.

kinglove1211 said:
Wish I had this a month ago, had to send my phone off to be jtagged. I'm sure I'll need it again. Thank you for your work.
Click to expand...
Click to collapse
I also went through it . Therefore, I decided to share this experience. :highfive:

ilia3367 said:
Link to download the attached files
https://drive.google.com/open?id=0B-o0d4PkVUwBflNNbF96UWx1N1JtVkY5S1JrM25lemIxVFgtTEdwb0lEUmxqYzlqc2VfZzg&authuser=0
Click to expand...
Click to collapse
Latest Radio / Firmware ?
Where's the img of recovery, I need?

@ilia3367,
Thank you for the great contribution, it is good to know you are unbrickable with these tools.

Great info should be in android development

arohrmann said:
Latest Radio / Firmware ? Where's the img of recovery, I need?
Click to expand...
Click to collapse
Firmware - 21.44.12
Radio - MDM9625_104351.17.02.71.13R
IMG recovery need not.

Will this technique work on a Droid Maxx?
Sent from my XT1254 using XDA Free mobile app

Too bad we can't use this to reprogram the turbos to be the xt1250 so that the bl can be unlocked.I bricked my phone purposely to try and flash the XML of the moto maxx and it will only let me flash the system for the turbo.It does unbrick your phone though,did it 3 times in a row so it definitely works.

failed to flash gpt.bin
When i try to flash the given files, flashing of gpt.bin results into "remote failure" and says "preflash validation failed". Rest all the files are flashed perfectly. But cannot flash gpt.bin. Please help

chiranjiv97 said:
When i try to flash the given files, flashing of gpt.bin results into "remote failure" and says "preflash validation failed". Rest all the files are flashed perfectly. But cannot flash gpt.bin. Please help
Click to expand...
Click to collapse
This method is intended for Verizone Motorola Droid Turbo. gpt.bin for this phone . What's your phone? Try to flash through motofastboot.

ilia3367 said:
This method is intended for Verizone Motorola Droid Turbo. gpt.bin for this phone . What's your phone? Try to flash through motofastboot.
Click to expand...
Click to collapse
I
Yess I know, I used Motorola droid turbo Verizon xt1254, running on quark 21.44.12. I'm not quite sure about how to use the motofastboot? It'll be great if you can help, thanks a lot

chiranjiv97 said:
I'm not quite sure about how to use the motofastboot? It'll be great if you can help, thanks a lot
Click to expand...
Click to collapse
Download this archive https://drive.google.com/open?id=0B-o0d4PkVUwBR0FiUHNKRUxIXzQ&authuser=0
Unpack it to C: \ drive
Copy this folder gpt.bin
Flash it command - mfastboot flash partition gpt.bin

have you tried the mot dev manager? that should detect a brick and set back to factory. rsdlite could also be used

This happened to my phone and I tired using the TURBO-UNBRICK you provided, but it gets to 'flashing singleimage' and I get 'Target ERROR: 7 - Open multi failed, unkown error FAILED (sdl-transfer-image:send-image:sdl-open-multi:target error)
My phone bricked after I started the Lollipop update. No idea what happened. I started the update, went back to work, checked half an hour later and phone was dead. Any help would be great, this is the closest I've gotten to getting it fixed.
~Zanny

Anybody tried this tools for xt1254 ?

will this work if i bricked it after installing 5.1?

I did everything descripted in this thread, but my device keeps rebooting (I can hear the USB disconnecting and reconnecting) and still shows up as a QDLoader in device manager. Plus the screen is still black. Any toughts?
Edit: is this singleimage (msimage_901_0228_0000) right? Usually it's a .bin file, but this one is a .mbn

ilia3367 said:
Download this archive
Unpack it to C: \ drive
Copy this folder gpt.bin
Flash it command - mfastboot flash partition gpt.bin
Click to expand...
Click to collapse
Hey, sorry was away! but the link is broken, it says removed due to violation of terms :/ and i cannot post the link in the quote coz xda is preventing me -.-

[Q] nexus 7 (2012) tablet, soft bricked, can't flash images, failed, unknown error

i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

stargirl29 said:
i have a Nexus 2012 7inch tablet (Wifi) that is soft bricked. (stuck at the perpetual moving colored dots screen).
when my tablet was still under warranty in 2013 it did have it's motherboard replaced when it wouldn't even turn on. now the problem is different, at least i can power it on and get into the bootloader. since the lollipop update it had been getting progressively laggy before finally 'crashing' and bootlooping.
i've tried the following:
1) first i attempted the tutorial located here: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
i managed to wipe the device but not flash the images to the device.
2) then i used this tutorial http://forum.xda-developers.com/showthread.php?t=2588979 to install the adb drivers.
3) i have now used Wugs to attempt flash stock + unroot. everything seems to work until it gets to "sending 'system'" then it gives "FAILED <data transfer failure <Unknown error>>, also same error for sending 'userdata'and post-flash factory reset. same Unknown error.
i am also not sure which google images to use. i have tried nakasi 4.3 (JWR66Y), 4.4.4 (KTU84P), and 5.1.1 (LMY47V), and "any build" options.
so i'm not sure if it could be a driver issue or how to fix it further. fastboot seems to recognize the tablet while adb does not. i did not have it set in debugging mode.
i've attached the screen from Wugs...
Click to expand...
Click to collapse
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.

fastboot
Evolution_Tech said:
Try flashing the images individually with fastboot. That's how I always do it. Be sure your platform tools are up to date as well.
Click to expand...
Click to collapse
i'm not really sure how to do that.

stargirl29 said:
i'm not really sure how to do that.
Click to expand...
Click to collapse
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot

fastboot
Evolution_Tech said:
Download and unzip the factory image. Unzip two times until you have all the images. I.E. bootloader, radio, boot, system, recovery, userdata, cache.
Put them where fastboot can find them. I.E. platform tools folder.
Hopefully you know how to use fastboot.
Start by flashing bootloader.
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
Then flash the rest.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot format cache
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.

stargirl29 said:
no i do not know how to use fastboot. but what you posted sounds exactly like the tutorial that i followed in step #1 that i mentioned above. i did the tutorial again last night and was able to flash the images this time, but it's still stuck in bootloop on startup.
Click to expand...
Click to collapse
Factory reset from recovery.

Evolution_Tech said:
Factory reset from recovery.
Click to expand...
Click to collapse
if you mean this, https://support.google.com/nexus/answer/4596836?hl=en
yes. that was the first thing i did. and always the first thing i try before using any toolkits or manual repairs.
i ran Wugs again today and FINALLY got it back to the sign in screen to setup the tablet. everything was going great. then i got back into the bootloader to lock the oem. and when it restarted i'm still getting the "optimizing apps x of 99" which is annoying but it seems my tablet is at least usable for now.

Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.

fixed it!
vipthomps said:
Sorry to say your in the same boat as a large number of people. These devices just up and died. Take a look around for #Nexus7Bricked
Google forums will also confirm this. At this time you have a nice paperweight. I've tried all the things you have (and spent probably 10 hours over a few months) and it still won't come up.
Click to expand...
Click to collapse
i fixed it with Wugs yesterday, finally! after 5 days of trying.

Magisk for Android 12/OOS12 global ( magisk_patched)

Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

suhuf said:
Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
How exactly do we
suhuf said:
Magisk for Android 12/OOS12 global ( magisk_patched)
IN2015_11.C.11 (Global)
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Just flash this via fastboot?

scorpio76r said:
How exactly do we
Just flash this via fastboot?
Click to expand...
Click to collapse
fastboot flash boot boot.img

suhuf said:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
If you're sure the version is global, it should work.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
Read the explanation and remove the original boot file and fastboot, the phone will boot.
Put the same boot file in the download section of the phone and patch it with magisk, then upload the patched file to the phone with fastboot process.
[TOOL] A QUICK Android OTA payload dumper
Made with Go. By utilizing goroutines, this can extract img files from (full) OTA payload.bin really quickly. See how fast this is: https://i.imgur.com/adpijqf Source Code: https://github.com/ssut/payload-dumper-go Prebuilt binaries...
forum.xda-developers.com

Apologies but I'm confused by the steps in the posts above... Can someone post a brief step-by-step guide for this? Thanks!
[EDIT] nevermind, extracted and patched on my own, thanks!

scorpio76r said:
Just did this and now I'm stuck fastboot. I even tried fastboot reboot and still stuck in fastboot on the device. I'm using Windows PowerShell btw
Click to expand...
Click to collapse
I also got stuck on fastboot. Any solution will be appreciated.
Edit: Had to restore device with MSM Download Tool.

Hi, just updated to official OOS12 and hate it, it appears it also re locked my bootloader which was unlocked, how do I unlock it again? do I follow the same steps? I want to go back to OOS11 and start flashing custom roms
edit: just checked on fastboot mode. it says unlocked in red letters. would still like to flash magisk!

cjvzla said:
Hi, just updated to official OOS12 and hate it, it appears it also re locked my bootloader which was unlocked, how do I unlock it again? do I follow the same steps? I want to go back to OOS11 and start flashing custom roms
Click to expand...
Click to collapse
You sound like me a week ago. Best bet is to msm your phone and start from scratch. Bring your phone up to 11.10.10 then go with the Jaguar rom. It has March security patch, call record and developers literally responds within a few minutes of a post or question.

scorpio76r said:
You sound like me a week ago. Best bet is to msm your phone and start from scratch. Bring your phone up to 11.10.10 then go with the Jaguar rom. It has March security patch, call record and developers literally responds within a few minutes of a post or question.
Click to expand...
Click to collapse
hi, just checked and I still have the bootloader unlocked, which means I could flash a recovery right? I haven't flashed stuff in android phones in a while and I'm a bit rusty, where should I go first?

cjvzla said:
hi, just checked and I still have the bootloader unlocked, which means I could flash a recovery right? I haven't flashed stuff in android phones in a while and I'm a bit rusty, where should I go first?
Click to expand...
Click to collapse
Yes use fastboot twrp image from the official twrp thread. Then install twrp installer.

krakout said:
Apologies but I'm confused by the steps in the posts above... Can someone post a brief step-by-step guide for this? Thanks!
[EDIT] nevermind, extracted and patched on my own, thanks!
Click to expand...
Click to collapse
hi! how did you extracted and patched? did you follow the video? cause I can't understand what hes saying. can you leave me a step-by-step? thanks. I'm on OOS12, bootloader unlocked

cjvzla said:
hi! how did you extracted and patched? did you follow the video? cause I can't understand what hes saying. can you leave me a step-by-step? thanks. I'm on OOS12, bootloader unlocked
Click to expand...
Click to collapse
I just sent you a personal message with a link that will help you out.

Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.

krakout said:
Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.
Click to expand...
Click to collapse
Yes, using windows 10 pc.

krakout said:
Sorry, couldn't reply earlier.
Higher in this thread there's a link for a very useful program. Use that program to rip everything from the official download update package (have you downloaded that?). Then move boot.img to your phone, and let Magisk Manager patch it. Then copy the patched file over to your PC and use adb to flash it.
Click to expand...
Click to collapse
hi thanks for the tutorial, managed to extract the OOS12 stock boot img and patched it with magisk 24, but when I connect in fastboot mode and check with the fastboot devices command I get nothing, and nothing on device manager either. even tho my bootloader is unlocked and fastboot drivers are installed, the pc doesnt seem to "see" my phone?
the adb devices command does show my phone when connected and turned on.

That's a bit tricky and I'm not sure why it would do that, never encountered it... Tried restarting adb?

krakout said:
That's a bit tricky and I'm not sure why it would do that, never encountered it... Tried restarting adb?
Click to expand...
Click to collapse
looked for the latest drivers and installed those, now my devices does show up with the fastboot devices command! do I test the patched boot img first? and did you flash it normally or did you use fastboot flash boot_a and fastboot flash boot_b for the a/b partitions?