Related
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.
Hello People !!!
Want to return your OP2 to 100% Stock Factory Image or have you soft bricked OP2 and nothing except fastboot works or you need OxygenOS fastboot images ? This is the thread for you !!
Download Fastboot Image from here :- https://mega.nz/#!itR00ZaI!gJ6T0jgqfZaIF9NLlCzWj4LIGMMhCw8m8owFdeB_2B4
Extract the Zip in a folder .
Boot the phone into fastboot.
Run the batch file.
Done.
This method WILL NOT WIPE DATA
If you want to wipe data to,flash userdata.img from here :- https://www.androidfilehost.com/?fid=24052804347833307
Use command
fastboot flash userdata userdata_64.img
Click to expand...
Click to collapse
You need the latest adb/fastboot package to be successful.For that,do this :-
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only)
Extract the zip and place the android-sdk-windows folder on your desktop.
Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):-
Tools > Android SDK Tools, Android SDK Platform-tools- Extras > Android Support Library, Google USB Driver
Click to expand...
Click to collapse
Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
Thanks for reading ...
Credits :- @jcespi2005 For making the fastboot zip ... @Naman Bhalla for making the thread and partitions images thread.
Done to @jcespi2005 here :- http://forum.xda-developers.com/donatetome.php?u=281521
Donate to me here :- http://www.amazon.in/gp/registry/wishlist/1X55WMSVTW3KW/
Thanks again. !!
This method has been tested successfully by atleast 2 people ,including me
This img is oxygen os 2.1.1?
Sent from my Nexus 5 using XDA Free mobile app
matitorres07 said:
This img is oxygen os 2.1.1?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Correct
DEAD
OMG MY OPT IS DEAD... dont start just vibrate and flashing dont star...i cant went in to the recovery mode...just on fastboot HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP
S0ad113 said:
OMG MY OPT IS DEAD... dont start just vibrate and flashing dont star...i cant went in to the recovery mode...just on fastboot HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP
Click to expand...
Click to collapse
i've got the exact same problem. Let me guess: your bootloader is locked?
anyways, try this: press POWER + VOLUME UP until you're in fastboot mode. connect the OP2 to your PC and execute the command 'fastboot continue' in a cmd window. if not, repeat until it works. your phone should boot like normal, you can't restart or shutdown though, since you'll be stuck in the same loop again.
at least that's my problem. can't flash anything since bootloader is locked, ADB does work fine though, as long as the phone is running.
really sucks to need a PC everytime you want to power on your phone.. if anyone can help, i'd gladly appreciate it
S0ad113 said:
OMG MY OPT IS DEAD... dont start just vibrate and flashing dont star...i cant went in to the recovery mode...just on fastboot HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP
Click to expand...
Click to collapse
I TRY TO USE TOOLBOX and try to flash..some via CMD But give me error writing "recover" ...Failed Remote: device is Locked. Cannot Flash images)
Helppppppp me
---------- Post added at 11:13 PM ---------- Previous post was at 11:08 PM ----------
rattig said:
i've got the exact same problem. Let me guess: Your bootloader is locked?
Anyways, try this: Press power + volume up until you're in fastboot mode. Connect the op2 to your pc and execute the command 'fastboot continue' in a cmd window. If not, repeat until it works. Your phone should boot like normal, you can't restart or shutdown though, since you'll be stuck in the same loop again.
At least that's my problem. Can't flash anything since bootloader is locked, adb does work fine though, as long as the phone is running.
Really sucks to need a pc everytime you want to power on your phone.. if anyone can help, i'd gladly appreciate it
Click to expand...
Click to collapse
i try all always locked always loop omg
---------- Post added at 11:38 PM ---------- Previous post was at 11:13 PM ----------
Helpppppppppppppppppppppppppppppppppppppppppppppppppppppppp
Please note that on the fastboot userdata command you are missing a letter. You have "fastboot flash userdata userdata_64.img" and it should be fastboot flash userdata userdata_64G.img. Great job by the way, used it to reset the OP2 and works great.
ukcain said:
Please note that on the fastboot userdata command you are missing a letter. You have "fastboot flash userdata userdata_64.img" and it should be fastboot flash userdata userdata_64G.img. Great job by the way, used it to reset the OP2 and works great.
Click to expand...
Click to collapse
I did it..but is not that the problem....the problem is..when i try to flash some...fail always. give the error : device is Locked. Cannot Flash images
REBORN
Solved ty allll
How on earth did you manage to get a fastboot image for the OP2?
Thanks by the way
Stevles said:
How on earth did you manage to get a fastboot image for the OP2?
Thanks by the way
Click to expand...
Click to collapse
Converting the .DAT inside the official recovery ZIP to .IMG format
The rest of partitions are on the fastboot format, so only system and cache needs conversion, and userdata comes from hydrogenOS fastboot package...
jcespi2005 said:
Converting the .DAT inside the official recovery ZIP to .IMG format
The rest of partitions are on the fastboot format, so only system and cache needs conversion, and userdata comes from hydrogenOS fastboot package...
Click to expand...
Click to collapse
Nice
is not flash me the file system.img
i get error message "the app crash" from windows
pls help
Zahi122 said:
is not flash me the file system.img
i get error message "the app crash" from windows
pls help
Click to expand...
Click to collapse
I'm having the same issue
I'll try to do it through TWRP and see if that works for me
Naman Bhalla said:
Hello People !!!
Want to return your OP2 to 100% Stock Factory Image or have you soft bricked OP2 and nothing except fastboot works or you need OxygenOS fastboot images ? This is the thread for you !!
Download Fastboot Image from here :- https://mega.nz/#!itR00ZaI!gJ6T0jgqfZaIF9NLlCzWj4LIGMMhCw8m8owFdeB_2B4
Click to expand...
Click to collapse
Hi,
Are these images from a Chinese, EU or US version of the device?
thanks
Hello all,
is there a new img.image?
I have great problems and need a super clean install included wipe data!!
Thanxx for helping
S5 & One + Boeffla Inside
S0ad113 said:
Solved ty allll
Click to expand...
Click to collapse
How? What did you do different? For me, the fastboot.exe stops working at the below step.
..\fastboot>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
avi0889 said:
How? What did you do different? For me, the fastboot.exe stops working at the below step.
..\fastboot>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
I got the same error at first then I copied all the files into my platform-tools dir that has ADB & fastboot then run it.
Try this tool. It works good for me. But the windows driver for OP2 and the Qualcomm Diagnostic 9006 Driver must be installed.
Sry, can`t post the link. please PN.
Worked great, but it switched my wifi off. Even if I turn it on manually it doesn't show any active networks. I have rebooted several times. Any workaround?
hello
i tried to install twrp but the swipe didn't work
so i tried to install an older version
but now when i reboot twrp do not appear
and i have no more than 800mo memory available
i can't hard reset
what can i do ?
noogpout said:
hello
i tried to install twrp but the swipe didn't work
so i tried to install an older version
but now when i reboot twrp do not appear
and i have no more than 800mo memory available
i can't hard reset
what can i do ?
Click to expand...
Click to collapse
Flash recovery from CMD !
AbhaYsinGH007 said:
Flash recovery from CMD !
Click to expand...
Click to collapse
how can i flash recovery from cmd ?
where can i download the file ?
noogpout said:
how can i flash recovery from cmd ?
where can i download the file ?
Click to expand...
Click to collapse
Xiaomi.eu -> https://xiaomi.eu/community/threads/twrp-for-mi-pad-3.39743/
i follow the thread you mention
i can launch twrp but swipe do not work, i have now an otg cable but mouse is not recognized
so i don't know how to flash the rom
noogpout said:
i follow the thread you mention
i can launch twrp but swipe do not work, i have now an otg cable but mouse is not recognized
so i don't know how to flash the rom
Click to expand...
Click to collapse
That could be a bug !
noogpout said:
i follow the thread you mention
i can launch twrp but swipe do not work, i have now an otg cable but mouse is not recognized
so i don't know how to flash the rom
Click to expand...
Click to collapse
I find that hard to believe. Did you follow post #10? At your own risk, of course.
Guys, I did it!
I had no problems with the touchscreen, so there was nothing to solve for me. My Bootloader was also unlocked already.
Here is everything I did (be careful, this deletes all your data!):
Boot into fastboot (Volume down+ Power on, hold the Volume down-Key until fastboot loads)
Code:
fastboot -w
fastboot erase system
fastboot format system
fastboot flash recovery twrp.img
Boot into TWRP (Volume up + Power on, hold the Volume up-Key until TWRP boots)
WIPE -> Data -> Repair or Change File System -> Resize File System
Flash xiaomi.eu-zip normally (hopefully) enjoy!
Click to expand...
Click to collapse
Read the entire thread
yes i read the entire thread, i executed all the flashboot command but my rom was a global one not chinese, so the touch screen does not work in twrp.
Actually i downloaded a rom here : https://drive.google.com/uc?id=0B023gSzruW0aLV9ZRG1pdHpqd3c&export=download
then in fast boot mode i executed this command : ./flash_all.sh
but at the end i have this error : finished. total time: 10.194s
error: cannot load './images/cust.img'
i cannot boot to miui but now i have MI Recovery instead of TWRP
noogpout said:
yes i read the entire thread, i executed all the flashboot command but my rom was a global one not chinese, so the touch screen does not work in twrp.
Actually i downloaded a rom here : https://drive.google.com/uc?id=0B023gSzruW0aLV9ZRG1pdHpqd3c&export=download
then in fast boot mode i executed this command : ./flash_all.sh
but at the end i have this error : finished. total time: 10.194s
error: cannot load './images/cust.img'
i cannot boot to miui but now i have MI Recovery instead of TWRP
Click to expand...
Click to collapse
Why would you execute "./flash_all.sh". Did you try the methods mentioned on page 2 in the thread?
You need to know your commands.
Do you have ADB drivers installed?
Palm Trees said:
Why would you execute "./flash_all.sh". Did you try the methods mentioned on page 2 in the thread?
You need to know your commands.
Do you have ADB drivers installed?
Click to expand...
Click to collapse
yes i know the command : ./flash_all is a script in the archive : cappu_images_7.5.11_20170514.0000.00_7.0_global_xiaomi.eu.zip
i have already tested the commands in the page 2 :
fastboot -w
fastboot erase system
fastboot format system
fastboot flash recovery twrp.img
twrp is ok but i cannot swipe, because the touch screen is not enabled
so i cannot pass the step :
10. WIPE -> Data -> Repair or Change File System -> Resize File System
it's ok i commented the following lines in the script :
fastboot $* flash cust `dirname $0`/images/cust.img
if [ $? -ne 0 ] ; then echo "Flash cust error"; exit 1; fi
so the script can continue and after the boot is ok, MIUI start
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?
root: for A.87 stock rom
Unlock bootloader and place the mentioned two files to Platform tools folder on your pc.
Download "vbmeta.img" and "Magisk_patched.img"
• adb devices
• adb reboot bootloader
•fastboot devices
• fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
• fastboot flash boot magisk_patched.img
• fastboot reboot
+++±+++++++
Guide to flash Recovery
- Connect your phone to PC, Allow USB Debugging. Now Type These Commands.
adb reboot bootloader
fastboot devices
fastboot reboot bootloader
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery recoveryname.img
fastboot reboot recovery
To keep custom recovery flash twrpkeep.zip when's booted to recovery :
Bro my device is a.89 ..is this vbmeta working...?
qeb said:
Bro my device is a.89 ..is this vbmeta working...?
Click to expand...
Click to collapse
Yes it work on all a10 update
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
misiek998 said:
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
Click to expand...
Click to collapse
oh, thank's men. edited.
Hello, Can I use the VBMeta on android 11 or no? thanks!
Ryeeeeel said:
Hello, Can I use the VBMeta on android 11 or no? thanks!
Click to expand...
Click to collapse
Can't root rui 2.0 (Android 11), and can't install custom recovery except "los recovery" but can't do any thing with it just wiping cache and data partition.
do not try to flash custom recovery on realme ui 2.0 , it will brick your device
I need to ask, this guide will work with A88/A89 update?
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
adamuadamu said:
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
Click to expand...
Click to collapse
Yes. Just flash the original firmware using SP Flash-Tools. However, youmust make sure it is the full 7-8 GB ROM, and not an OTA file. Also, ensure that you are flashing the correct ROM for your model. If your model is an RMX2155, you'll need to follow this guide steps 1-through-to-10 (inclusive):
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
If it is any other model, just do what is said to work. Unfortunately, I don't know much about the other versions.
thanks the explanation.
I've found a 2155 ROM or at least a file that's said to be - ie. I've found a file 'RMX2155export_11_C.09_2021070809260000', extracted that, there was a huge file 'RMX2155export_11_C.09_2021070809260000.ofp' inside; using oppo-decrypt from github I've got bunch of files with names that seem to be SPFlashTool ROM.
Assuming it's a proper ROM: if I have already unlocked the bootloader, do I have to flash the rom and do the 10 steps from the tutorial or could I replace recovery.img and magisk-patched boot.img and flash rooted rom immediately? Sorry if it sound noobish, but I don't want to brick the phone.
I'm curious to try to go back to stock ROM for a while, because of call quality (I believe changing it to Vietnam needed for unlock made the call quality worse) and to check the camera and it's libraries - I'm running crdroid, photo quality is disappointing no matter what GCam/settings/tweaks I use and there are only imx682/imx471 libs on the phone there are samsung libs, but diagnose apps like aida show the main sensor is imx682, but the EU version of realme 7 is said to have different back camera sensor (GM1). Not sure if RMX2151 ROMs would include proper GM1 libs if that's true about sensor differences between RMX2151 and 2155.