Related
Passing my P3 on to my wife and need to get it back to stock.
Got as far as loading the 3.2 firmware from sammobile using fastboot as Odin won't flash.
It recognises an OTA update but fails to download the update. I actually think that it fails to install but in any event it get stuck.
The kernel is still at 2.6.36.3 and baseband is the P7500 one.
I think that the kernel is located in the boot.img but it doesn't look like I am able to overwrite it with fastboot.
The bootloader seems to be replaced but I still have a unlocked bootloader.
Any ideas?
Thanks
GaryWS said:
Passing my P3 on to my wife and need to get it back to stock.
Got as far as loading the 3.2 firmware from sammobile using fastboot as Odin won't flash.
It recognises an OTA update but fails to download the update. I actually think that it fails to install but in any event it get stuck.
The kernel is still at 2.6.36.3 and baseband is the P7500 one.
I think that the kernel is located in the boot.img but it doesn't look like I am able to overwrite it with fastboot.
The bootloader seems to be replaced but I still have a unlocked bootloader.
Any ideas?
Thanks
Click to expand...
Click to collapse
You need to restore the stock recovery as well, ClockworkMod Recovery wont handle OTA updates.
Do fastboot flash recovery [recovery img] to reflash the stock recovery.
To re-lock the bootloader, try fastboot oem lock (not tried).
Note that it appears that even if relocking the bootloader, manufacturers have ways of knowing if the bootloader has been unlocked. However, since the purpose is to give it to someone else with possibly less technical skills (that does not require the feature), a locked bootloader is an added security.
pruano said:
You need to restore the stock recovery as well, ClockworkMod Recovery wont handle OTA updates.
Do fastboot flash recovery [recovery img] to reflash the stock recovery.
To re-lock the bootloader, try fastboot oem lock (not tried).
Note that it appears that even if relocking the bootloader, manufacturers have ways of knowing if the bootloader has been unlocked. However, since the purpose is to give it to someone else with possibly less technical skills (that does not require the feature), a locked bootloader is an added security.
Click to expand...
Click to collapse
thx pruano, the stock firmware contains a recovery image. This writes ok ... I also tried locking the bootloader - it locks ok but with the same results
It looks like the kernel might be the problem ...
GaryWS said:
thx pruano, the stock firmware contains a recovery image. This writes ok ... I also tried locking the bootloader - it locks ok but with the same results
It looks like the kernel might be the problem ...
Click to expand...
Click to collapse
Did you flashed ALL the imgs (boot.img, recovery.img and system.img) from the PDA archive?
You can always erase/format the partitions with fastboot erase/format [boot|recovery|system] before re-flashing the images... (important note: if you erase/format the boot partition, do not leave recovery without flashing a new boot img).
I would also restore the stock modem (you need the one from P7100BUKE2, as P7100BULB4 does not have it) - for this you will need Odin.
pruano said:
Did you flashed ALL the imgs (boot.img, recovery.img and system.img) from the PDA archive?
You can always erase/format the partitions with fastboot erase/format [boot|recovery|system] before re-flashing the images... (important note: if you erase/format the boot partition, do not leave recovery without flashing a new boot img).
I would also restore the stock modem (you need the one from P7100BUKE2, as P7100BULB4 does not have it) - for this you will need Odin.
Click to expand...
Click to collapse
Pruano, using fastboot, the erase command seems to work but format does not. Why do you say that I need Odin to flash the modem? I have done this with fastboot previously using "fastboot flash radio modem.img" ...
Edit: Pruano, you put me onto the right track. The modem was the problem. Once I got the original modem from P7100BUKE2 installed it all worked fine - even with unlocked bootloader.
and just for interest i had to use: "fastboot flash modem modem.img"
GaryWS said:
Why do you say that I need Odin to flash the modem? I have done this with fastboot previously using "fastboot flash radio modem.img" ...
Edit:and just for interest i had to use: "fastboot flash modem modem.img"
Click to expand...
Click to collapse
Did not know fastboot would recognize that partition, not on the docs.
Always learning.
GaryWS said:
Edit: Pruano, you put me onto the right track. The modem was the problem. Once I got the original modem from P7100BUKE2 installed it all worked fine - even with unlocked bootloader.
Click to expand...
Click to collapse
Yes, unlocked bootloaders do not interfere with OTAs
Regarding the modem, in truth it was a long shot, just a step to restore to pristine state.
The knowledge that the P7500 modem works best with custom ROMs and flashing it as a common procedure is relatively new, no wonder one had to guess that it would interfere with OTAs (as its not obvious, probably the OTA install does some kind of background safety check using the modem firmware as base); good to know for the future.
odin'd ND7 for the correct model i605 from a site other than sammobile (download was really slow), everything went through fine when it went to reboot it does a quick boot loop
cannot go to recovery mode, but can go to odin.
cannot flash full tar back to it, it fails on sboot
So I downloaded the file from sammobile and extracted it
thinking maybe I have to make a flash file without the bootloader if possible?
extracted the tar
boot.img
cache.img
hidden.img
modem.bin
recovery.img
sboot.bin
system.img
tz.img
edit. used pit file with odin (read in other threads after the fact) and all seems clear, very noob of me -.-
normally don't have to use it...
anyways still want to know if possible to make without bootloader and/or make something like this:
http://forum.xda-developers.com/showpost.php?p=24278264&postcount=9
Hi all!
Occasionaly flashed blue spark twrp v41 (for OOS 3.x) while on Sultans ROM with locked bootloader.
No root access, didn't flash supersu. Kingroot and other 'on one click' methods somehow don't work.
Now, when I try to use fastboot to flash recovery it denies as bootloader is locked. When I try to unlock bootloader using 'oem unlock' it tries to boot recovery which doesn't boot (stucks on logo).
Any chance to solve without hardbricked solution?
I'm on OOS 2.2.2 and have done the same thing (flashed blu spark v41)... same result as you though, a phone I can only boot into fastboot mode
This was the advice I was given (from OnePlus forums)...
https://forums.oneplus.net/threads/...lus-logo-help-me-please.462406/#post-15248530
Here are the steps to get TWRP without messing up your recovery partition
>> Grab Bootloader file (emmc_appsboot.mbn) from OxygenOS Lollypop stock rom
>> Place it in Adb& fastboot folder and flash it via fastboot
fastboot flash aboot emmc_appsboot.mbn
>> Now Type
fastboot reboot-bootloader
>> Now temporarily boot TWRP official recovery for OPX with fastboot
fastboot boot "yourTWRPfileNAME.img"
You should be able to boot to TWRP recovery now
After Flashing and stuff reboot to fastboot and
>> Grab Bootloader file (emmc_appsboot.mbn) from Oxygen OS Marshmallow stock rom
>> Place it in Adb& fastboot folder and flash it via fastboot
fastboot flash aboot emmc_appsboot.mbn
Reboot and enjoy
Click to expand...
Click to collapse
Edit: Maybe you'll need to flash the emmc_appsboot.mbn file from the Sultans ROM though???
The above didn't work for me. I had to UnBrick
You cannot install a recovery on locked bootloader,your phone is not going into stock recovery because of some boot failure, just turn off your phone remove battery if its removable then try again to go into recovery
Sent from my HUAWEI TIT-AL00 using XDA Forums
Hi,
After much read of guides, I post here my SIMPLE guide for OTA upgrades when your Moto G is unlocked and you use systemless root and TWRP.
This guide is safe and works!
For example, with this guide you can upgrade from STOCK MPJ24.139-23.4 to MPJ24.139-63:
Warning: I assume you know the concepts "fastboot", "systemless root" and TWRP.
For the original stock firmware search here for your exact MODEL and VERSION: http://mirrors.lolinet.com/firmware/moto/athene/official/
1) Reboot to TWRP and make a FULL BACKUP of your current firmware. Use the SD-Card and not the internal memory.
2) To Apply the OTA you need to restore BOOT.IMG and SYSTEM.IMG.
2a) If you rooted your device, for sure your BOOT.IMG isn't the original one. You can:
- Option 1: Restore it from an original backup of your firmware (if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "boot.img" and flash it in the fastboot mode using "fastboot flash boot boot.img".
2b) If you use Systemless SuperSU then your system partition can be untouched. In case of doubt, or if the patch shows an error, you can restore it...
- Option 1: Restore it from one backup of your firmware (only if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "system.img_sparsechunk.0-7" and flash them in the fastboot mode using these 8 commands (execute one, wait until completes, then execute the next one):
Code:
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
3) Boot to the TWRP Custom Recovery (you don't need to restore the original Recovery partition).
4) Download the OTA (Blur_Version.24.24.4.athene.retail.en.US.zip) or copy it from the downloaded directory. Copy the ZIP file to a computer, extract the file "/META-INF/com/google/android/updater-script" and edit it... Remove these three lines (this only removes the check of the running build, because you like to execute it inside TWRP):
Code:
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-63/64:user/release-keys" ||
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-23.4/4:user/release-keys" ||
abort("Package expects build thumbprint of 6.0.1/MPJ24.139-63/64:user/release-keys or 6.0.1/MPJ24.139-23.4/4:user/release-keys; this device has " + getprop("ro.build.thumbprint") + ".");
After that, copy (repack) this edited file to the ZIP file of the OTA. I suggest to change the name of the ZIP, for example to "Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip". Now, you can run this patch file running TWRP.
5) Copy the patch OTA file to the SD-CARD, boot to the TWRP and apply the OTA... After several minutes the task completes. Reboot and check if the update is done and all works well. Your data needs to be already there...
6) Reboot into the fastboot mode and reflash the TWRP Custom Recovery using "fastboot flash recovery twrp-3.0.2-0-athene.img". Then boot in the recovery mode and do another Backup (for save untouched "system.img" and "boot.img" partitions).
7) Now you can re-root using the TWRP mode and SuperSU 2.78 in Systemless mode (remember to execute "echo SYSTEMLESS=true>>/data/.supersu" prior to install the SuperSU.zip)
I hope this helps you!
This guide only uses the minimum and required steps.
:good:
If you like to download one already patched OTA, then download it from here (join the two files first!):
Part 1: http://www.sendspace.com/file/dkws7p
Part 2: http://www.sendspace.com/file/xaompg
Part 1: http://www.sendspace.com/file/e3of46
Part 2: https://www.sendspace.com/file/a3tl4r
CRC:
filename=Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip
size=508332365
crc32=AFEC5752
Thank you, I was wondering about just this. Will come In handy.
Do you need to resign the zip with signapk?
Thanks for you guide!
I used it to update my Lenovo P2 to Nougat.
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Indianvixen9 said:
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Click to expand...
Click to collapse
I've heard this from a few people. I got the Amazon variant little more than a week ago. Unlocked BL and rooted lickety splits, no issues.
I consider myself pretty tech savvy, but the post might as well have been in Swahili. Can it be dumbed down any further?
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
t0mm13b said:
Do you need to resign the zip with signapk?
Click to expand...
Click to collapse
No, just re-zip! :victory:
Dbush72 said:
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
Click to expand...
Click to collapse
Done! :highfive:
Thank you for the reply and refreshing the download links
As far as I can tell you are flashing this via TWRP which is why the zips dont need signed is that correct?
I have an xt1625 non-amazon version that im working with.
I tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml which didnt work with this error:
E3005: "EMMC:/dev/block/bootdevice/by-name/boot:
has unexpected contents
I also tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml
Failed with the same error as last time
I also tried flashing Blur_Version.24.31.48.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml which does seem to pass the version checks but gives this error:
"eom/app/BRApps2/oat/arm/BRApps.odex" has unexpected contents.
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?