I flashed wrong baseband/modem files on oxygen os 3.1.4 and now i am stuck at oneplus logo.I can only boot into fastboot mode not even custom recovery.
Please help!!!!!!
saagr_2800 said:
I flashed wrong baseband/modem files on oxygen os 3.1.4 and now i am stuck at oneplus logo.I can only boot into fastboot mode not even custom recovery.
Please help!!!!!!
Click to expand...
Click to collapse
Was on 3.1.4 around 7 months ago. Do you have EFS backup? If don't, that was a big mistake flashing new baseband without backup.
But here some advices to do:
→Boot to fastboot and re-check if bootloader still unlocked (if yes then proceed ↓ )
→Flash the stock MM recovery for OOS within fastboot
→Directly boot to recovery (using fastboot command or manually)
→Reflash the full ROM 3.1.4 zip. It should bring back everything
*Or try to flash compatible TWRP for 3.1.4 and just restore the EFS partition or full Nand Backup (if you have one)
*If not, then you'll need to follow mega unbrick guide.
oneplus x fastboot images of rom
seacowx said:
Was on 3.1.4 around 7 months ago. Do you have EFS backup? If don't, that was a big mistake flashing new baseband without backup.
But here some advices to do:
→Boot to fastboot and re-check if bootloader still unlocked (if yes then proceed ↓ )
→Flash the stock MM recovery for OOS within fastboot
→Directly boot to recovery (using fastboot command or manually)
→Reflash the full ROM 3.1.4 zip. It should bring back everything
*Or try to flash compatible TWRP for 3.1.4 and just restore the EFS partition or full Nand Backup (if you have one)
*If not, then you'll need to follow mega unbrick guide.
Click to expand...
Click to collapse
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?
saagr_2800 said:
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?
Click to expand...
Click to collapse
Thats disaster. Have you tried any steps i suggested earlier?
Re-check unlocked bootloader? and try flashing compatible TWRP within fastboot? hows the results?
• Download full ROM 3.1.4 zip and place in your computer (ADB folder)
• Directly boot to TWRP and use "ADB sideload" of full ROM zip (using ADB command)
Use search button (or just google it) how to use ADB sideload.
→Worst case scenario, follow the mega unbrick guide that should help you. OK. goodluck.
Note: Easiest way, contact oneplus support team for remote session. They will help you
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
try that
can't flash factory oneplus rom from recovery
saagr_2800 said:
Bro i have messed with oneplus x,I have deleted all the data inside now i can only boot to fastboot mode,can u please help me finding fastboot images of any rom for oneplus x?
Click to expand...
Click to collapse
Bro i somehow fastboot firmware and radio files now i can access recovery ,i tried to install factory oneplus oos 3.1.4 but i get these red lines saying
could not find META-INF/com/google/android/update-binary
error installing .zip
failed to mount '/firmware' (invalid argument)
failed to mount '/system' (invalid argument)
saagr_2800 said:
Bro i somehow fastboot firmware and radio files now i can access recovery ,i tried to install factory oneplus oos 3.1.4 but i get these red lines saying
could not find META-INF/com/google/android/update-binary
error installing .zip
failed to mount '/firmware' (invalid argument)
failed to mount '/system' (invalid argument)
Click to expand...
Click to collapse
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
These commands helped me
saagr_2800 said:
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
These commands helped me
Click to expand...
Click to collapse
What twrp version are you on?
You need a stock MM recovery for opx to flash full 3.1.4.
and make sure you ain't got corrupted zip file. Download full 3.1.4 ROM zip from onplus website.
seacowx said:
What twrp version are you on?
You need a stock MM recovery for opx to flash full 3.1.4.
and make sure you ain't got corrupted zip file. Download full 3.1.4 ROM zip from onplus website.
Click to expand...
Click to collapse
I tried from mm recovery as well it says installation failed
saagr_2800 said:
I tried from mm recovery as well it says installation failed
Click to expand...
Click to collapse
If you're already on stock MM recovery. then just reflash the OOS full ROM 3.1.4 zip. (The zip you tried was corrupted one, i guess). re-download and try again.
Note: make sure to checked box mount (system, data, cache) only, before flashing full ROM.
dchrono said:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
try that
Click to expand...
Click to collapse
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way
Part.0 said:
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way
Click to expand...
Click to collapse
You know what, It's a bit old and hectic dealing with stock MM things.. Plus messing up with modem with no backup preparation. It's more like complicated hell
IF only he wanna try flash any N custom ROM for opx,
(At least to get or to make sure your device get booted back first)
I could suggest him the proper procedure IF he want to.
seacowx said:
You know what, It's a bit old and hectic dealing with stock MM things.. Plus messing up with modem with no backup preparation. It's more like complicated hell
IF only he wanna try flash any N custom ROM for opx,
(At least to get or to make sure your device get booted back first)
I could suggest him the proper procedure IF he want to.
Click to expand...
Click to collapse
lmao, yeah that was terrible gambling without having a backup!
anyway how to backup modem/baseband? do u have link refers to that? thanks
Part.0 said:
lmao, yeah that was terrible gambling without having a backup!
anyway how to backup modem/baseband? do u have link refers to that? thanks
Click to expand...
Click to collapse
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
seacowx said:
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
Click to expand...
Click to collapse
lol, nice thanks a lot man! im not intend to messing up with my modem either lol
Part.0 said:
sorry, does it make any difference?
his situation was having a bootloop/softbrick and couldnt boot into system nor recovery at all,, all partition has been wiped,,the only thing that working is fastboot (now he has recovery).
as i know "fastboot erase modemst1/2" is for fixing network/gps/wifi issue on booted state device. Cmiiw
The only way is, he could try reflash full ROM zip using stock recovery or custom ROM using TWRP with proper way
Click to expand...
Click to collapse
To repair EFS issues when fastboot only available. There are other ways as well however OP mentioned fastboot available only.
Edit: @Part.0 if you would have read OP correctly, you would have noticed he mentioned that he flashed the wrong modem files and my solution along with a fastboot reboot which I didn't mention would have solved his problem. fastboot erase modemst1/2 although you only know it for solving modem/GPS issues are also partitions. Remember our job here is not to convince @Part.0 of our solutions, next time a thank you would do well for teaching you something.
seacowx said:
If you're already on stock MM recovery. then just reflash the OOS full ROM 3.1.4 zip. (The zip you tried was corrupted one, i guess). re-download and try again.
Note: make sure to checked box mount (system, data, cache) only, before flashing full ROM.
Click to expand...
Click to collapse
I tried oneplus rom with oneplus recovery,before installing i also did wipe and cache,it failed.
I also tried installing lineage os using twrp but there it says
could find meta-inf/com/google/android/update-script not found
and failed to mount './firmware' (invalid argument)
saagr_2800 said:
I tried oneplus rom with oneplus recovery,before installing i also did wipe and cache,it failed.
I also tried installing lineage os using twrp but there it says
could find meta-inf/com/google/android/update-script not found
and failed to mount './firmware' (invalid argument)
Click to expand...
Click to collapse
Ok since i can't reproduce your issue on this one, so i can't find the right solutions for your case.
• Unlocked bootloader + Working Recovery + Fastboot + Full ROM zip file
Those should enough fixing your issue.
Perhaps i missed something, like corrupted partitions (firmware). Maybe another user experienced with the issue can help you out.
Best luck for you.
Note: Maybe our friend here can help you out @dchrono or willing to help you. Thank you.
Ps: Try mountng of "Firmware" in mount section before flashing full ROM. So it will mounted (Firmware, System, data, cache) But wait, ask out before you do. Finger crossed
Download these files
https://www.androidfilehost.com/?fid=24269982087019810
http://www.mediafire.com/file/8g9v5fsslnbf1r6/Qualcomm+Driver+Setup.zip
1 switch off Oneplus x forced
2 install Qulacomm usb driver
3 press volume up button n connect with PC
4 extract Oneplus x unbrick tool
5 run msm downloder and click on start
6 if complete flashing flash stock ROM via memory card
Contact me on. WhatsApp if not success
+917756968834
seacowx said:
Here you go, in case someone try messing up with the modem make sure to backup modemst1 & modemst2 first:
Just open terminal emulator on device and types:
su (to grant root access)
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
*It will copy the 2 files into sdcard/internal storage. Save those 2 files to safety place. like a Bank
To restore (using fastboot) types:
fastboot flash modemst1 modemst1.bin
fastboot flash modemst2 modemst2.bin
Click to expand...
Click to collapse
can it be done with TWRP recovery?
CRN-TWRP 3.2.1
Download here,
https://mega.nz/#!9gV0RQ7C!tcxUtoJisxdQbGWh62Te69TnKYXlUXv-L1p8_kknxS4\
!!unlocked bootloader
Yes, it does support GSI roms.\
Tested PIE roms. (not tested oreo)
- AEX
-Descendant
-RR
-Viper
-Lineage
To flash
1 Reboot to bootloader mode (volume down + power button)
2 fastboot flash recovery "recovery name plus extension or just drag recovery on cmd) then hit enter
3. Reboot to recovery
4 Profit:good:
Bugs
-Decryption password fails
Want to disable dm verity and force encryption?
Follow link
1 Format data
2. Reboot to recovery
3 Flash force encryption disabler
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
++Base recovery, Lenovo A6000
Reserved
is there a reason why this phone won't flash TWRP or ROMS directly from TWRP?
buschris said:
is there a reason why this phone won't flash TWRP or ROMS directly from TWRP?
Click to expand...
Click to collapse
It actually does that
Question on which partitions to backup in twrp. I'm on stock pie Moto g6 xt1925-6 and want to be able to flash back to it with no problems. Normally I would backup boot, data, system. If I want to try out a gsi however it's is a system image and that's not normally backed up in twrp. I guess I'm asking which partitions should I backup that allows moving between gsi images, stock rom and custom roms.? Thanks
Skippy12359 said:
Question on which partitions to backup in twrp. I'm on stock pie Moto g6 xt1925-6 and want to be able to flash back to it with no problems.lNormally I would backup boot, data, system. If I want to try out a gsi however it's is a system image and that's not normally backed up in twrp. I guess I'm asking which partitions should I backup that allows moving between gsi images, stock rom and custom roms.? Thanks
Click to expand...
Click to collapse
System.img is just the format the ROM (GSI) comes in. A regular system backup will restore just fine. The only difference is you can flash and backup system as an image if you want with TWRP now (boot and recovery too).
Data backups only work if you unencrypted your data. So restoring stock without root isn't possible (because of DM verity and forced encryption).
But restoring system and boot should work either way between GSI's. But unencrypted GSI backups of system and data should restore either way. You can make the backups as images if you want.
madbat99 said:
System.img is just the format the ROM (GSI) comes in. A regular system backup will restore just fine. The only difference is you can flash and backup system as an image if you want with TWRP now (boot and recovery too).
Data backups only work if you unencrypted your data. So restoring stock without root isn't possible (because of DM verity and forced encryption).
But restoring system and boot should work either way between GSI's. But unencrypted GSI backups of system and data should restore either way. You can make the backups as images if you want.
Click to expand...
Click to collapse
Really great feedback madbat99 and very much appreciated. Cheers
Nice to see, especially since Best Buy is running a sale on the G6 Unlocked (all of $150USD) - their cheapest Universal Unlocked handset during the current sale; at this price, even cheapskates like my Mom and her fiance could bite. (Further, at this price, we could even buy three - and I could run Lineage OS again - since Tracfone does not care if I don't run stock.)
the roms never start on my moto g6 . except the descendant.
tiagoneo said:
the roms never start on my moto g6 . except the descendant.
Click to expand...
Click to collapse
What other roms did you try?
tiagoneo said:
the roms never start on my moto g6 . except the descendant.
Click to expand...
Click to collapse
am having this issue with stock pie.
I run the flashing commands, some gives few errors as Key siganuteres or something. and finally doesnt boot.
I use same commands but with Oreo Stock Rom and phone starts working.
here is code I used
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase
fastboot oem fb_mode_clear
fastboot reboot
I ask to myself If I will take same luck with the custom roms.
maybe am a bit offtopic...
yurais said:
am having this issue with stock pie.
I run the flashing commands, some gives few errors as Key siganuteres or something. and finally doesnt boot.
I use same commands but with Oreo Stock Rom and phone starts working.
here is code I used
I ask to myself If I will take same luck with the custom roms.
maybe am a bit offtopic...
Click to expand...
Click to collapse
You can't use the exact same commands. Open the XML file in the zip and see what the flash commands are
Thanks, didnt know the important stuff was inside the XML, will check...
Enviado desde mi SM-G930F mediante Tapatalk
---------- Post added at 10:02 AM ---------- Previous post was at 09:33 AM ----------
madbat99 said:
You can't use the exact same commands. Open the XML file in the zip and see what the flash commands are
Click to expand...
Click to collapse
Ok. I checked the xml, compared with bat file and there were significant changes.
Vendor partition was not beeing flashed
There was no erase ddr command
And the order of commands is slightly different.
I CORRECTED, flashed, again saw the strange warning or error while flashing recovery and boot which read: Image signed with key bad key
But system booted this time... even though digitizer still doesnt work, my main purpose of uograding, as it stopped working when I flashed the previous running oreo version...another story, offtopic here
Thanks
Enviado desde mi SM-G930F mediante Tapatalk
I had tested the RR, AEX, HAVOC OS, LINEAGE. now it only starts if I install the stock from scratch, and put the gsi system image. but does not pick up with gapps
dmilz said:
CRN-TWRP 3.2.1
Download here,
https://mega.nz/#!9gV0RQ7C!tcxUtoJisxdQbGWh62Te69TnKYXlUXv-L1p8_kknxS4\
!!unlocked bootloader
Yes, it does support GSI roms.\
Tested PIE roms. (not tested oreo)
- AEX
-Descendant
-RR
-Viper
-Lineage
To flash
1 Reboot to bootloader mode (volume down + power button)
2 fastboot flash recovery "recovery name plus extension or just drag recovery on cmd) then hit enter
3. Reboot to recovery
4 Profit:good:
Bugs
-Decryption password fails
Want to disable dm verity and force encryption?
Follow link
1 Format data
2. Reboot to recovery
3 Flash force encryption disabler
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
++Base recovery, Lenovo A6000
Click to expand...
Click to collapse
dmilz said:
CRN-TWRP 3.2.1
Download here,
https://mega.nz/#!9gV0RQ7C!tcxUtoJisxdQbGWh62Te69TnKYXlUXv-L1p8_kknxS4\
!!unlocked bootloader
Yes, it does support GSI roms.\
Tested PIE roms. (not tested oreo)
- AEX
-Descendant
-RR
-Viper
-Lineage
To flash
1 Reboot to bootloader mode (volume down + power button)
2 fastboot flash recovery "recovery name plus extension or just drag recovery on cmd) then hit enter
3. Reboot to recovery
4 Profit:good:
Bugs
-Decryption password fails
Want to disable dm verity and force encryption?
Follow link
1 Format data
2. Reboot to recovery
3 Flash force encryption disabler
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
++Base recovery, Lenovo A6000
Click to expand...
Click to collapse
qual é a chave de decodificação?
UPHtx said:
qual é a chave de decodificação?
Click to expand...
Click to collapse
[TWRP][UNOFFICIAL] TWRP [64 Bit][3.7.0]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
I'm a noob.i wanna try out a custom kernel but i got no idea what steps to follow
Backup Boot-Partition with TWRP
Install another Kernel, whipe cache and dalvic
Boot Device
Restore Boot-Partition and the new Kernel is gone / whipe cache and dalvic
Boot Device
https://www.youtube.com/watch?v=rKHswG2Nytw
Ashiq.makkar said:
I'm a noob.i wanna try out a custom kernel but i got no idea what steps to follow
Click to expand...
Click to collapse
1. make sure the kernel of your choice SUPPORTS your DEVICE, flashing wrong kernel means BYE BYE POCO
2. using custom Recovery like twrp/blackpitch/orangeFox etc just flash the Kernel.zip file! and wipe cache/delvik
3. flash Magisk19.3 if you wana root your device!
however we don't flash kernels via fastboot but for your knowledge if you extract the kernel.zip and take the img file from inside and place it in
C:\Program Files (x86)\Minimal ADB and Fastboot
open adb command window and flash kernel with this command
Code:
fastboot flash boot kernel.img
will flash the kernel in /boot section
later you can install mangisk manager and PATCH the boot.img
see METHOD 2 https://www.thecustom droid.com/install-magisk-root-android-devices/
however 99% fellows here uses twrp! its easy and popular!
YasuHamed said:
1. make sure the kernel of your choice SUPPORTS your DEVICE, flashing wrong kernel means BYE BYE POCO
2. using custom Recovery like twrp/blackpitch/orangeFox etc just flash the Kernel.zip file! and wipe cache/delvik
3. flash Magisk19.3 if you wana root your device!
however we don't flash kernels via fastboot but for your knowledge if you extract the kernel.zip and take the img file from inside and place it in
C:\Program Files (x86)\Minimal ADB and Fastboot
open adb command window and flash kernel with this command
will flash the kernel in /boot section
later you can install mangisk manager and PATCH the boot.img
see METHOD 2 https://www.thecustom droid.com/install-magisk-root-android-devices/
however 99% fellows here uses twrp! its easy and popular!
Click to expand...
Click to collapse
thanks.did the twrp method and everything worked out fine
You can enable Auto brightness in any gsi rom..I made a special vendor.img file to enable it..
Required things:
1.unlocked bootloader.
2.working brain.
Steps:
1.Download and extract zip file from below link.
https://drive.google.com/file/d/1Bxhuj-GLByS5rf_w53mQTGK1GmnmDZzs/view?usp=drivesdk
You get 3 file vbmeta.img,vendor.img,boot.img(this file is for redmi 9 (Lancelot).do not flash those file on other phone which code name is not Lancelot)
2.flash vbmeta.img and boot.img via fastboot mood with below cmd
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
3.flash vendor.img via fastbootd mood with below cmd
fastboot flash vendor vendor.img
4. erase all userdata and boot your device .Now your auto brightness work...
Error fix:
1."file size is larger then partition size"if you get this type of Error then you need to type below cmd in fastbootd mood.
fastboot resize-logical-partition vendor 780
2.If you face any boot loop after flash and not solve it via erasing userdata the you need to flash magisk patch boot.img which you currently use:good::good:...evenif you get bootloop then first flash global v11.0.4.0 fastboot rom then follow my instruction again..
3.If brightness slider not work or headphones not detect then follow the below post.
https://forum.xda-developers.com/showpost.php?p=83635205&postcount=1
4.If you do not know how to flash gsi on redmi 9 (Lancelot) then follow below link.
https://forum.xda-developers.com/showpost.php?p=83533901&postcount=1
prove:
I provide a zip file link as attachment.unzip it and you get a video prove...
If my process work for you then don't forget to thanks me because it is free....
What have you done to the vbmeta?
koso000 said:
What have you done to the vbmeta?
Click to expand...
Click to collapse
Nothing but add some overlay file to vendor image. It is difficult now because we cannot Mount vendor image via custom recovery so I Mount it in Linux and some overlay file and give them permission that's it...
I nothing done with vbmeta.img. it is a blank file so no need to worry about it
It didn't work for me..could you share a guide to generate fix for my own vendor