Related
Hi Folks,
i am a noob and have just started picking up the tricks of the trade.i have an unbranded htc desire. Was using the HiAPk rom till now. Then thought of flashing the INsertcoin 1.1.2. Created EXT4 for the same and recopied all data to my sdcard. Now when i try to flash any rom it just gets caught at the boot screen. Hi dont have a recovery image. But i do have a nandroid backup. Restoring the backup is not helping as well. The phone is s-off,rooted with clockword recovery 2.5.0.7. i do have access to recovery but, whatever i do, the phone gets stuck at the boot screen. Please assist. I guess this occured when i accidentally selected/deselected hboot/fastboot option? can that be a potential cause?
Try and go into recovery then wiping Data/Cache, then go to advanced -> wipe dalvik cache and reboot. If it doesnt work, reflash the rom and do the above steps again and reboot. See if it works
EddieN said:
Try and go into recovery then wiping Data/Cache, then go to advanced -> wipe dalvik cache and reboot. If it doesnt work, reflash the rom and do the above steps again and reboot. See if it works
Click to expand...
Click to collapse
Tried doing the above steps but still caught at the boot screen whenever i reboot. Though the rom got installed but, on rebooting the same boot screen staring at me
What version recovery do you have? Try updating it, although remember that having a nandroid backup from an older recovery wont restore if you are on a newer recovery. So maybe it isn't a good idea to update your recovery if you only have a nandroid from an older recovery.
BEFORE READING ON: What partitions are you using? It could be that the new ROM you want to flash doesn't fit in the current partitions you have flashed. Stock? CM7r2? Oxygen?
----------------------------------------------------------------------------
Try with Fasboot Commander v1.51 (http://forum.xda-developers.com/showthread.php?t=1193915).
Here are steps I used last night when I was in the same situation as you:
1.Once you download Fastboot Commander, make sure you have the latest java downloaded on your PC (java.sun.com).
2.Once you've done that, open up Fastboot Commander on your PC, then boot your phone using Vol Down + Power and choose "FASTBOOT".
3.Then, connect your phone to your PC using a USB cable and go to the "misc" tab in Fastboot Commander and click "Check connection", and if it's successful, then choose "print device info" so you see everything is OKAY.
4.Paste the "Device Info" here too so we can see what's up!
5. On the same "misc" tab in Fastboot Commander, tick the boxes in the "Erase partitions": System, Cache, Boot
6. Click "Erase Chosen Partitions"
7. Choose "BOOTLOADER" on your phone display, and when it's done, disconnect the USB cable.
8. Flash the new ROM as usual, while doing a full wipe right after you flashed it (still in recovery): Dalvik/Data/Cache
9. Reboot when done and hopefully it will work.
If it doesn't work, I think it will be that you are trying to install a ROM which supports a different partition table than what you have flashed, which is causing the bootloops because of the lack of space on the partitions needed.
Good luck
EddieN said:
What version recovery do you have? Try updating it, although remember that having a nandroid backup from an older recovery wont restore if you are on a newer recovery. So maybe it isn't a good idea to update your recovery if you only have a nandroid from an older recovery.
BEFORE READING ON: What partitions are you using? It could be that the new ROM you want to flash doesn't fit in the current partitions you have flashed. Stock? CM7r2? Oxygen?
----------------------------------------------------------------------------
Try with Fasboot Commander v1.51 (http://forum.xda-developers.com/showthread.php?t=1193915).
Here are steps I used last night when I was in the same situation as you:
1.Once you download Fastboot Commander, make sure you have the latest java downloaded on your PC (java.sun.com).
2.Once you've done that, open up Fastboot Commander on your PC, then boot your phone using Vol Down + Power and choose "FASTBOOT".
3.Then, connect your phone to your PC using a USB cable and go to the "misc" tab in Fastboot Commander and click "Check connection", and if it's successful, then choose "print device info" so you see everything is OKAY.
4.Paste the "Device Info" here too so we can see what's up!
5. On the same "misc" tab in Fastboot Commander, tick the boxes in the "Erase partitions": System, Cache, Boot
6. Click "Erase Chosen Partitions"
7. Choose "BOOTLOADER" on your phone display, and when it's done, disconnect the USB cable.
8. Flash the new ROM as usual, while doing a full wipe right after you flashed it (still in recovery): Dalvik/Data/Cache
9. Reboot when done and hopefully it will work.
If it doesn't work, I think it will be that you are trying to install a ROM which supports a different partition table than what you have flashed, which is causing the bootloops because of the lack of space on the partitions needed.
Good luck
Click to expand...
Click to collapse
Hi, was using a HiApk ROM till now which needs no partitions at all. Also i agree that it might be the case that the new rom which i want to flash is not supporting the partitions(no reasons why HiAPK shouldnt run coz had been running it without partitions for the past 2months). Before going ahead ,do u think i should i re-format my sdcard to FAT32 and delete the partitions..Just in case this doesnt work out i go ahead with the fastboot commaHer. Whatever you suggest is what i am going to do. Thanks.
Getshivang89 said:
Hi, was using a HiApk ROM till now which needs no partitions at all. Also i agree that it might be the case that the new rom which i want to flash is not supporting the partitions(no reasons why HiAPK shouldnt run coz had been running it without partitions for the past 2months). Before going ahead ,do u think i should i re-format my sdcard to FAT32 and delete the partitions..Just in case this doesnt work out i go ahead with the fastboot commaHer. Whatever you suggest is what i am going to do. Thanks.
Click to expand...
Click to collapse
Also the new ROM that i was trying to flash requires a 1gb ext2/3/4. So i did a 1 gb Ext4 partition. This one is the stable insertcoin 1.1.2
Getshivang89 said:
Hi, was using a HiApk ROM till now which needs no partitions at all. Also i agree that it might be the case that the new rom which i want to flash is not supporting the partitions(no reasons why HiAPK shouldnt run coz had been running it without partitions for the past 2months). Before going ahead ,do u think i should i re-format my sdcard to FAT32 and delete the partitions..Just in case this doesnt work out i go ahead with the fastboot commaHer. Whatever you suggest is what i am going to do. Thanks.
Click to expand...
Click to collapse
EDIT: Forgot to mention that in order to use Fastboot Commander you'll need the ADB drivers. Just install HTC Sync to get the drivers for it!
Since you say in the beginning that you are S-Off and have Recovery 2.5.0.7, the only things I can think of that you haven't done are this:
1. Insertcoin 1.1.2 (http://forum.xda-developers.com/showthread.php?t=1016940&highlight=insertcoin) says you need to be S-off (which you are), and have the latest recovery (5.0.1.0). So my first piece of advice would be to update your recovery to 5.0.1.0 from what you have now (2.5.0.7) but remember what I said about nandroid backups and recovery earlier on!!
2. Make sure you have a 1GB Ext2, Ext 3 or Ext4 partition on your SD-card. The way to partition your SD-card is here: http://forum.xda-developers.com/showpost.php?p=7279872&postcount=3
Insertcoin says it should work on the stock HBOOT which I'm assuming you have since you said you've never flashed another partition table on your phone.
So basically, update your recovery (best done with Fastboot Commander imo) and make sure the md5 sums match up. Once you've updated your recovery, make sure your SD card is ready, then wipe everything in recovery and reflash the rom, and wipe everything in recovery again before rebooting.
Again, remember that since you made your nandroid backup in CWM 2.5.0.7, it wont be able to restore in CWM 5.0.1.0 so basically once you update your recovery your nandroid from 2.5.0.7 will be useless.
EddieN said:
EDIT: Forgot to mention that in order to use Fastboot Commander you'll need the ADB drivers. Just install HTC Sync to get the drivers for it!
Since you say in the beginning that you are S-Off and have Recovery 2.5.0.7, the only things I can think of that you haven't done are this:
1. Insertcoin 1.1.2 (http://forum.xda-developers.com/showthread.php?t=1016940&highlight=insertcoin) says you need to be S-off (which you are), and have the latest recovery (5.0.1.0). So my first piece of advice would be to update your recovery to 5.0.1.0 from what you have now (2.5.0.7) but remember what I said about nandroid backups and recovery earlier on!!
2. Make sure you have a 1GB Ext2, Ext 3 or Ext4 partition on your SD-card. The way to partition your SD-card is here: http://forum.xda-developers.com/showpost.php?p=7279872&postcount=3
Insertcoin says it should work on the stock HBOOT which I'm assuming you have since you said you've never flashed another partition table on your phone.
So basically, update your recovery (best done with Fastboot Commander imo) and make sure the md5 sums match up. Once you've updated your recovery, make sure your SD card is ready, then wipe everything in recovery and reflash the rom, and wipe everything in recovery again before rebooting.
Again, remember that since you made your nandroid backup in CWM 2.5.0.7, it wont be able to restore in CWM 5.0.1.0 so basically once you update your recovery your nandroid from 2.5.0.7 will be useless.
Click to expand...
Click to collapse
Logs as asked:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
-----------------------------------.
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 6.93.1002.
Radio version: 5.11.05.27.
Main software version: 2.29.405.5.
cid: htc__001.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
-----------------------------------.
STARTING ERASE OF PARTITION(S).
Erasing partition "boot" - PLEASE WAIT.
boot erased SUCCESSFULLY.
Erasing partition "system" - PLEASE WAIT.
system erased SUCCESSFULLY.
Erasing partition "cache" - PLEASE WAIT.
cache erased SUCCESSFULLY.
FINISHED ERASING PARTITION(S).
Getshivang89 said:
Logs as asked:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
-----------------------------------.
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 6.93.1002.
Radio version: 5.11.05.27.
Main software version: 2.29.405.5.
cid: htc__001.
cpld: none.
product: bravo.
mid: pb9920000.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
-----------------------------------.
STARTING ERASE OF PARTITION(S).
Erasing partition "boot" - PLEASE WAIT.
boot erased SUCCESSFULLY.
Erasing partition "system" - PLEASE WAIT.
system erased SUCCESSFULLY.
Erasing partition "cache" - PLEASE WAIT.
cache erased SUCCESSFULLY.
FINISHED ERASING PARTITION(S).
Click to expand...
Click to collapse
Hey Eddie N,
Just one thing. Now just to get back to the ROM i was running till now, should i just flash HiAPK now after doing all those steps as u suggested? Once i get through with this i can go ahead to flash insertcoin. But , first priority now is to just run the phone out of the boot screen in HiAPK(as it requires no partitioning/no recovery issues).. Thanks for the invaluable help. I am gonna keep u posted
I'd do this now:
Nandroid back to your HiAPK, then get RomManager and in Rom Manager update your CWM from 2.5.0.7 to 5.0.1.0 (the EASIEST way). Do a nandroid backup right away through rom manager after installing the new recovery so you can always go back if something goes wrong!! Reboot to recovery and reflash insertcoin.
After doing that you should have what's needed to run insertcoin (S-Off, latest recovery, Stock hboot, 1gb ext2/3/4). Before you didn't have latest recovery and you changed SD-card but i assume you fixed your SD-card now
If nandroiding back doesn't work, reflash it from scratch. If THAT doesn't work I'm not quite sure how to help you further I'm new myself but managed to fix my bootloop last night with the method i gave you
EddieN said:
I'd do this now:
Nandroid back to your HiAPK, then get RomManager and in Rom Manager update your CWM from 2.5.0.7 to 5.0.1.0 (the EASIEST way). Do a nandroid backup right away through rom manager after installing the new recovery so you can always go back if something goes wrong!! Reboot to recovery and reflash insertcoin.
After doing that you should have what's needed to run insertcoin (S-Off, latest recovery, Stock hboot 130mb system, 1gb ext2/3/4). Before you didn't have latest recovery and you changed SD-card but i assume you fixed your SD-card now
Click to expand...
Click to collapse
You are the man!!!yes i changed my sd card now. MAybe my sd card has gone bad. No wonder i couldnt flash any rom..Now back to HiAPK. I am gonna setup my sdcard again using gparted. Dont rely think the partitioning tool i was using till now was wrking(perhaps damaged my sd card) Thanx a lot mate
Just checked.. The phone was loading up even without the sd card(the one suspected of having gone kaput). But, now when restart the phone with that sd card it gets stuck at the boot screen. Any reason why this can be happening?
Seriously.. there should be sticky saying that stuck at htc screen, or bootloop is not a brick.
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error while restoring /system!
I did nothing but boot into recovery and this is all that happens when trying to recover my cwm backups. The version of CWM should not have changed and I've flashed these files before. I accidentally started another backup and shut the phone off while it was plugged in through usb (debugging might have been enabled but I don't use adb commands or have a shell).
I can restore my rom but I want to restore my backup.
How can I know the version of the backups and see if they are different from the cwm recovery version? Also in the past I have flashed and backup through rom manager, but would my rom manager boot into cwm recovery load a different cwm recovery (it shouldn't)?
I also tried this...reload the rom but restore each partition except for system, but it fails on data too then.
At a loss here. I love my backup. I was just a system camera apk away from perfection
Please help
Solution: 5 hours of playing around and the solution is that you need to make sure the cwm version is always the same...through rom manager.
I was attempting to change my Galaxy Nexus from Cyanogenmod 10.2.1 to cm 11 (current stable release). So, I did the following:
Created a Nandroid backup, saved it to my laptop, and deleted it from my phone as after creating the backup I had almost no free space. Before deleting it, I did test it and confirm that it worked.
Downloaded the CM ROM and gapps from the CM website
Verified their hashes.
Copied them to /sdcard. I didn't think to verify their hashes again. This may well have been a mistake.
Used TWRP v2.6.3.0 to wipe the phone and attempt to install CM. A message appears: "Failed." Here's a sample output (note that the output falls off the right-hand edge of the screen and there seems to be no way to scroll it to make it readable):
Code:
Updating partition details...
Installing '/sdcard/cm-11-20150626-SNAPSHOT-XNG3
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard
Updating partition details...
At this point, the phone won't boot. It goes directly to recovery.
To recover, I thought I'd just copy over my Nandroid backup. But, I can't use adb in recovery. I tried to use fastboot to flash my nandroid backup, but the format seems to be different, and I wound up with a phone that, when attempting normal boot, gets stuck on the Google logo until I remove the battery. I do have access to recovery still.
How can I get something bootable on my phone? I just want to restore my Nandroid backup. (And maybe see if I can figure out why CM-11 didn't work.) I can't find any way to copy arbitrary files to my phone.
Solved
This guide enabled me to resolve my issue. The steps I took:
Downloaded the latest stock ROM for my phone
used fastboot to flash it following the instructions on the linked post (which involved unzipping things and whatnot)
Booted into the new system and restored /sdcard from backup
Copied the latest Nandroid backup to /sdcard
Restored the Nandroid backup
Tried to install CM 11 again (this time without deleting the backup from my phone). It failed, so I restored again and am giving up for now.
Quick question. I have unlocked my bootloader and flashed the latest factory image. Phone is working fine, stock and encrypted. I decided to flash TWRP 2.8.7.2 using adb. After flashing it, I can boot into it from the bootloader by selecting the recovery option. After that first time though, it reverts back to stock recovery. Any idea what I missed?
This happened to me too. If I remember correctly, after going into recovery from the bootloader, reboot again back to the bootloader and launch recovery again. Not exactly sure why, but doing it twice before booting to system did the trick.
jm.kloz said:
This happened to me too. If I remember correctly, after going into recovery from the bootloader, reboot again back to the bootloader and launch recovery again. Not exactly sure why, but doing it twice before booting to system did the trick.
Click to expand...
Click to collapse
I tried what you suggested and still no dice. I appreciate you trying though.
Sounds like Android is overwriting it with stock recovery. When you first booted into TWRP, did you see a message that said Allow Modifications, and swipe to allow it?
Sent from my Nexus 5X using Tapatalk
As thesoldier was asking, there is a new TWRP feature that allows you to only READ-ONLY the device to prevent any flags being set. This will allow you to make a backup of the system so that you can revert to it in the future for OTA updates as these updates look for any changes to the system. If it detects that the system has been mounted, it will not allow OTA updates. But installing TWRP this way prevents TWRP from modifying the ROM to prevent the stock recovery from reinstalling itself.
https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
"System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again."
Most likely you chose the option to not mount the system as read/write after installing TWRP. So after the next reboot, the system noticed a modification to the recovery partition, and restored the stock recovery.
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.