Develop Bugs

[Q] Flashing to pure stock 4.3 with the latest bootloader, recovery, etc.?

I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.

you didnt search very well...
there's a return to stock thread in the general section.

Just use this: http://forum.xda-developers.com/showthread.php?t=1766475
Read last 3-4 pages.

AbhishekS said:
I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.
Click to expand...
Click to collapse
search again... and in short if u are flashing your rom with stock image u dont have to install the bootloader and radio img again... search how to flash stock image using adb..
Sent from my Galaxy Nexus using xda premium

AbhishekS said:
I know this may have been answered several times. I did a search too, but to be honest couldn't find something to the point.
Can someone post an easy guide of the files to download and the commands to type in the Command Prompt to install 4.3?
I'm currently on 4.2.2 (LiquidSmooth). Rooted obviously with TWRP recovery. I have the ADB and fastboot drivers installed in my PC.
This is what I want to know.
1. Flashing pure stock 4.3 and wipe everything (including SDcard - I will take a backup)
2. Updating the bootloader
3. Updating the radio
4. Updating the stock recovery
5. Installing TWRP recovery for 4.3
Will be glad if someone could help me.
Thank you.
Click to expand...
Click to collapse
Hi, let me try to help you
Galaxy Nexus is my first smartphone. So i'm pretty new at flashing things. I did some research last year to learn how to flash stuff in it and that's how i learned to make a fresh install:
-Make sure you have the SDK platform-tools and the Galaxy Nexus driver properly installed on your PC. Also, make sure you have USB debuging enabled on your device.
-Download the factory image that fits your phone at https://developers.google.com/android/nexus/images
-Open up the tgz file you just downloaded and extract the files:
-boot.img
-bootloader-maguro-primemd04.img
-radio-maguro-i9250xxlj1.img
-recovery.img
-system.img
-userdata.img
Extract the files in the platform-tools folder to make things easier.
-Connect your Nexus to your PC, open the command prompt, go to the platform-tools folder and type
(Do not turn off, disconnect or close the cmd prompt windows until everything is done. Again, make sure you have the nexus driver properly installed on your Windows)
Code:
adb reboot-bootloader
(this command will reboot your device to recovery mode)
With your device on recovery mode, type the following commands to erase your device:
Code:
fastboot erase boot
Hit enter, then:
fastboot erase cache
Hit enter, then:
fastboot erase recovery
Hit enter, then:
fastboot erase system
Hit enter, then:
fastboot erase userdata
-Now you're going to flash the new files you have downloaded and extracted steps before:
Code:
fastboot flash bootloader bootloader-maguro-primemd04.img
(or whatever name your bootloader img file has. In this case the bootloader file is "bootloader-maguro-primemd04.img")
Code:
fastboot reboot-bootloader
(you'll need to reboot after flashing the bootloader)
Code:
fastboot flash radio radio-maguro-i9250xxlj1.img
Flash the radio
Code:
fastboot reboot-bootloader
Reboot again
Code:
fastboot flash system system.img
Flash system
Code:
fastboot flash userdata userdata.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot-bootloader
We are almost done!
Code:
fastboot erase cache
Code:
fastboot reboot
Done! Reboot to Android. The first boot may take some more time than the usual. Don't worry!
-
If you want to flash a custom recovery, download it from their website, go into fastboot mode and flash it using the command to flash the recovery.
Code:
fastboot flash recovery [recovery filename].img
The same command used when flashing the recovery on the fresh install above
That's the way i learned how to do it from scratch. In case someone more experienced has any thoughts about it, i'd like to hear as i'm not an expert and learned by researching it on my own...

This is how it's done, PROPER. Well done, mnoguti.
a maguro wrote this.

@mnoguti: You have said that to flash a custom recovery, one needs to go to the recovery mode and flash the custom recovery, but you said that flashing the stock recovery should be done in bootloader.
Is it fine to flash custom recovery from bootloader instead of recovery?

AbhishekS said:
@mnoguti: You have said that to flash a custom recovery, one needs to go to the recovery mode and flash the custom recovery, but you said that flashing the stock recovery should be done in bootloader.
Is it fine to flash custom recovery from bootloader instead of recovery?
Click to expand...
Click to collapse
you don't have to go into the recovery mode to flash recovery, just boot into fastboot mode and flash recovery using command:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
obviously replace the recovery.img with the name of the custom recovery file you downloaded, make sure the custom recovery file is in the same folder as fastboot/adb otherwise you'll have to do it like:
fastboot flash recovery C:\Downloads\recovery.img
Click to expand...
Click to collapse

Yes, that's what I thought. Thank you.
I had initially felt that stock recovery can flashed only in bootloader and custom recoveries can be flashed only by booting into stock recovery. But somewhere in my mind had a doubt on it and so asked. Thanks for clearing the doubt.
And a big thanks to @mnoguti for posting those steps. Worked like a charm for me.

Obviously he meant fastboot mode..
a manta wrote this.

AbhishekS said:
Yes, that's what I thought. Thank you.
I had initially felt that stock recovery can flashed only in bootloader and custom recoveries can be flashed only by booting into stock recovery. But somewhere in my mind had a doubt on it and so asked. Thanks for clearing the doubt.
And a big thanks to @mnoguti for posting those steps. Worked like a charm for me.
Click to expand...
Click to collapse
It's "fastboot mode". Sorry for the mistake!
I've updated my post and now it's right

[Q] How to update to 5.0.1 from a rooted 5.0 ?

Hello everyone,
Need some help here, i don't want to factoy flash again, i have a nexus 7 2013 wifi on Lollipop (5.0) rooted with a custom kernel and TWRP.
How to update with the new OTA to 5.0.1, without loosing data and without having FC after the flash ?
Is there a way to flash it with TWRP or with Nexus Root Toolkit ?

I read that i can download the 5.01 system image from Google, extract the system.img from it and flash it in fasboot and i will conserve my data and be updated to 5.0.1.
Is that correct and without issues?

^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.

Hi, this is a little off topic.
I have a 4.4.4 rooted one and it failed to update to 5.0.1. Now it says system is update even though it still 4.4.4. Is there anyway for me to fix it and get update?

yosmokinman said:
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Click to expand...
Click to collapse
Is running fastboot format cache necessary?

^I'm no expert but I can't see why not to run it, not going to hurt anything and could possibly save you some problems later.
anhhuy1605 I'd just go to the factory images page download it and do a full clean install. I would not recommend trying to upgrade from KK and keeping data. Though I'm sure it's worked fine for lots of people.

yosmokinman said:
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Click to expand...
Click to collapse
It's all done, i flashed only the system.img then TWRP and elementalx, i can't live without the DT2W.
Thank You for your very detailed post.

anhhuy1605 said:
Hi, this is a little off topic.
I have a 4.4.4 rooted one and it failed to update to 5.0.1. Now it says system is update even though it still 4.4.4. Is there anyway for me to fix it and get update?
Click to expand...
Click to collapse
First thing first:
1. Uninstall any mod and busybox and xposed (Make sur that your system is clean) thant Unroot with supersu
2. Flash the stock boot (kernel) and stock recovery
3. Sideload the ota for 5.0 and flash it
Hopefully it will be allright but don't forget to backup your data with titanium backup to your computer.

Hello eddy0147,
from where did you get the system.img for 5.0.1?
eddy0147 said:
It's all done, i flashed only the system.img then ...
Click to expand...
Click to collapse
Thanks!
tungdil

tungdil said:
Hello eddy0147,
from where did you get the system.img for 5.0.1?
Thanks!
tungdil
Click to expand...
Click to collapse
If you decompress the new Factory Image from here : https://developers.google.com/android/nexus/images
You're welcome

Thank you very much! :good:
Actually I expected that this factory image would also only contain a system.new.dat just like the LRX21P did before. That's why I din't even have a look at it. I just downloaded and extracted it, and could convert it to a mountable image (using simg2img)
Cheers,
tungdil
P.S.: Just finished flashing Stock 5.0.1 as secondary ROM with MultiROM after building a flashable zip using this system.img. Thanks again eddy0147 for the hint :good:

Help, possibly bricked phone

Hello, I am currently rooted and on stock on pixel xl. I am trying to flash the pure nexus rom. I downloaded through the link in the op, factory reset and flashed through twrp (3.0.2rc1). When I went to reboot, it said OS not installed. Can anyone offer any assistance with this? Needless to say, I didn't reboot with that. I did however do a backup (of stock) prior to this. I decided to restore my backup but when it rebooted it said something about the vender image is not right with this system and to flash the correct image. This is exactly what its saying : Your vendor image does not match the system. Please flash the NOF27C vendor image for your device. I have managed to move the correct image file to the internal storage but from what i read, can only install through twrp.
And when it finished rebooting, now 90% of my apps are crashing, no fingerprint hardware, developer options are not available and I had to reboot back into recovery but its like twrp is gone, it looks like the stock recovery. Somehow it appears there are parts of my stock rom and pure nexus rom combined which is understandbly causing my issues. Right now I am trying to get back to having twrp but am stuck.
I have since tried to reinstall twrp but when I plug my xl into my pc, the pc recognizes it but no storage. I cant move a file from pc to xl because its saying disconnected or not responding. Tried to get a command prompt and when I shift/right click, there is no option. I don't know what else to do.
If anyone has any suggestions, please help. I am freaking over this. Can't use my phone in the state its in.

Sounds far from bricked.
Just entirely screwed up.
FASTboot the latest factory image and then refrain from tinkering for the weekend.
These are the steps i use.
I think a new ADB/FastBoot package was released yesterday you might want to install that.
Execute fastboot commands (assuming the bin is on your PATH)
fastboot flash bootloader c:\_PIXEL_XL_\bootloader.img
fastboot reboot-bootloader
fastboot flash radio c:\_PIXEL_XL_\radio.img
fastboot reboot-bootloader
fastboot flash boot_a c:\_PIXEL_XL_\boot.img
fastboot flash boot_b c:\_PIXEL_XL_\boot.img
fastboot flash system c:\_PIXEL_XL_\system.img
fastboot flash system_b c:\_PIXEL_XL_\system_other.img
fastboot flash vendor c:\_PIXEL_XL_\vendor.img
fastboot flash modem c:\_PIXEL_XL_\modem.img
fastboot reboot
To add TWRP and Root:
fastboot boot c:\_PIXEL_XL_\twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip

TWRP not persistent

Hi guys,
I've just updated to newest OOS firmware wich is 5.1.2 and I'm facing a weird problem.
Every time I flash codeworks TWRP and reboot to system, the next time i try to boot to recovery it boots to the original recovery.
It's like when I flash TWRP it doesn't remain persistent. When i flash it through fastboot and straightly boot from fastboot to recoverry I succeed to get in TWRP but as soon as I reboot to system and try to boot to recovery I reach the original OnePlus recovery.
Is anyone facing the same problem ?
And also do you have any idea about what i could do to solve this problem ?
Thanks in advance for your answers !

If you don't have root or custom kernel its normal, plus you should use blu spark's twrp, its newer and more reliable.

Adnan008 said:
If you don't have root or custom kernel its normal, plus you should use blu spark's twrp, its newer and more reliable.
Click to expand...
Click to collapse
Indeed, I just needed to flash magisk to get it persistent. I'll try blu spark's one as you suggested.
Thank you very much for your answer !
Cheers !

Nothing to do with recoveries or kernel. After you do the fastboot flash recovery TWRP in fastboot, do this: "fastboot boot TWRP". I believe that's the right command. Basically after you flash it, manually boot to recovery through fastboot one time. After that it'll work from inside the phone or with the button combination with the phone off.

Jesus people are lazy these days.
First off there are official twrp versions for a reason!
Download the latest version: https://dl.twrp.me/dumpling/
Reboot into flash boot with the following command from your rom: adb reboot bootloader
With phone in fastboot mode: fastboot flash recovery 'twrp.img'
(You don't need to type out the entire file path you can just drag the file into the terminal and it'll insert the file location)
The reason you're not getting back into that recovery is because you're not booting into the recovery before you reboot into your ROM.
There is an option to boot straight into the recovery from the fastboot mode

pinnekeshaar said:
Jesus people are lazy these days.
First off there are official twrp versions for a reason!
Download the latest version: https://dl.twrp.me/dumpling/
Reboot into flash boot with the following command from your rom: adb reboot bootloader
With phone in fastboot mode: fastboot flash recovery 'twrp.img'
(You don't need to type out the entire file path you can just drag the file into the terminal and it'll insert the file location)
The reason you're not getting back into that recovery is because you're not booting into the recovery before you reboot into your ROM.
There is an option to boot straight into the recovery from the fastboot mode
Click to expand...
Click to collapse
Actually not that lazy because I used to do what you mentionned.
The thing is that a flash of Magik is needed to patch twrp. That's the step I forgot in the procedure and explained here.
So before being unpleasant, please know what you're talking about...
Cheers !

Question Pixel 6 Pro unbrick/recovery

Hello
I've just ordered my Pixel 6 Pro, coming from the OnePlus 8 Pro.
I love tinkering with Root/Kernels/Roms.
So my question is, if there is always a way to get back to stock in case of emergency?
The OnePlus phones are considered as "unbreakable", because You can ALWAYS unbrick it via MSM unbrick tool.
Would be nice to know when I start unlocking the bootloader of my Pixel
Thanks!

Sorry that Pixel doesn't have that unbrick tool ...
The only one is a batch commend file - Flash-All extracted from factory full ROM ...

It is possible to hardbrick a Pixel device without hopes of getting it running again, for example if you nuke your recovery.
Most softbricks can be solved by either doing what Kris Chen suggested, or by using
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair

After flashing a module that bootloops you can try this:
If it almost boots up but flashes, in a cmd window type:
adb wait-for-device shell magisk --remove-modules
It may grab that and remove all modules. If it doesn't, you can try this:
1. fastboot flash boot boot.img, reboot.
2. long press power button, then long press "power off", click ok to enter safemode.
3. Before your phone boots all the way up, boot to fastboot.
4. fastboot flash boot magisk_patched.img, reboot.
5. In cmd window type: adb wait-for-device shell magisk --remove-modules
6. Your phone will boot up with root and all modules removed.
There's a shortcut to safemode that removes everything but I'm not sure what it is.
Edit: boot.img is taken from the applicable firmware you are on downloaded from Google. Unzip the main zip, go into the folder and unzip the image zip that is inside.

Thank you all for your detailed information, very appreciated
Could someone check if the following is the right procedure to revert to stock kernel?
fastboot flash boot <magisk-patched-image>.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot (wait a bit, this takes a bit of time until you see the fastbootd screen)
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
And do I have to do this procedure everytime before switching from a custom kernel to another kernel?
Thanks!

Lycidias said:
Thank you all for your detailed information, very appreciated
Could someone check if the following is the right procedure to revert to stock kernel?
fastboot flash boot <magisk-patched-image>.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot (wait a bit, this takes a bit of time until you see the fastbootd screen)
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
And do I have to do this procedure everytime before switching from a custom kernel to another kernel?
Thanks!
Click to expand...
Click to collapse
Yes, correct, and yes, safest to do so each time switching kernels.