Develop Bugs

Mobile Version, Bootloop/Brick, Nandroid FAIL, Factory Flash FAIL, PLEASE HELP!!

HISTORY/CAUSE
Hi, so i was trying to manually install xposed (x80,sdk23).
I was confused at first about which version (arm, arm64, x86). I tried installing x86, it kept failing with 255 errors.
i tried arm(which is the correct one), which kept failing with 1 error. I installed it many times, and i think i once saw a not enough memory error. So i downloaded both arm and x86 xposed uninstallers. It still failed. Notice that after all this i was still able to boot up. I went into recovery and made a nandroid backup . Then i tried installing sdk22, and it showed that it was only for android 5.1. I uninstalled again and tried to boot up, but it was stuck in a bootloop. I booted into recovery, and tried to install the nandroid, but it failed with again 255 errors (only the system part)(does 255 errors again seems suspicious to you?). I tried a factory flash, it failed with unkwown command errors and invalid arguments.
CURRENT PROBLEMS
1. At first, the bootloop showed the 4 animated dots, but now it just goes black after the google logo.
2. The NANDROID backup failed, or more specifically the system restore part with 255 errors.
3. The FACTORY IMAGE flash failed, with invalid argument errors in sending things and unknown errors in rebooting into bootloader.
WORKING THINGS
1. Bootloader works
2. Recovery works
3. ADB & FASTBOOT works
4. The computer even recognises it as a device in recovery and gives me access to the data
DEVICE INFO
Device: Nexus 7 (2013) LTE Version, [deb],[razorg]
Android: Marshmallow 6.0.1 (MMB29Q)[Second to latest]
Bootloader: Flo-4.05
Recovery: TWRP 3.0.0-0
Warranty:Currently None

It's a very comprehensive description, thanks. Please do the following:
- boot TWRP
- connect PC
- run: adb shell dmesg > dmesg.txt
- find 'dmesg.txt' file in your adb folder
- attach it here or upload to http://pastebin.com

Soft bricked. phone not coming back

Okay so my phone was acting up a little where it was working fine and after a few days apps would start crashing so I would reflash the ROM I was using and it would be fine again for a few days and then it would happen again.
So I decided ill just go back to full stock and I went through the path of using the MSMdownloadtool.
So I put my phone into download mode and restored it. the first strange thing is when it was fully complete the device wouldnt reboot. it would seemingly go off and then default back to download mode and then the software would try and redo the process again even though it succeed.
So anyway I unplugged the device and booted it up. It got to the OOS boot animation and it just kept going and never booted. so I booted to Fastboot and flashed TWRP Blu-Spark and it just shows "Failed to mount '/system' (Invalid Arguement" (It shows it for cache, data etc.. aswell) and it also says "Updater process ended with ERROR: 7" when I try to flash anything.
Ive done this entire process like 5 times and it seems like no matter what i do I just cant get my phone booted into anything. Also whenever I turn my device off it seems to enter download mode as it shows up on my PC under COM connections and it takes holding down the power button for ages for it to come out of it
Am I screwed. thanks

LJAM96 said:
Okay so my phone was acting up a little where it was working fine and after a few days apps would start crashing so I would reflash the ROM I was using and it would be fine again for a few days and then it would happen again.
So I decided ill just go back to full stock and I went through the path of using the MSMdownloadtool.
So I put my phone into download mode and restored it. the first strange thing is when it was fully complete the device wouldnt reboot. it would seemingly go off and then default back to download mode and then the software would try and redo the process again even though it succeed.
So anyway I unplugged the device and booted it up. It got to the OOS boot animation and it just kept going and never booted. so I booted to Fastboot and flashed TWRP Blu-Spark and it just shows "Failed to mount '/system' (Invalid Arguement" (It shows it for cache, data etc.. aswell) and it also says "Updater process ended with ERROR: 7" when I try to flash anything.
Ive done this entire process like 5 times and it seems like no matter what i do I just cant get my phone booted into anything. Also whenever I turn my device off it seems to enter download mode as it shows up on my PC under COM connections and it takes holding down the power button for ages for it to come out of it
Am I screwed. thanks
Click to expand...
Click to collapse
Try the other versions of TWRP too, including the official.

tnsmani said:
Try the other versions of TWRP too, including the official.
Click to expand...
Click to collapse
Ive tried a modified TWRP, Blu-Spark and the latest official TWRP from their website and I still get failed to mount on all of the partitions.
When I look at any of the partitions it says
"/system File system: ext4 . Present: Yes . Removable: No . Size: 2913MB . Used: 4MB . Free: 2909MB . Backup Size: 4MB" I tried to change the file system but cant mount. any of them to even format" I get an ERROR code 8 if I try to repair the partition
If I try to flash anything I get "E1001: Failed to update system image" "Updater: process ended with ERROR: 7"

Oneplus 3 is bricked and found no way out yet

So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas on how to fix this?
Thanks in advance

EpicLawR said:
So i've bricked my oneplus 3 (oxygen 5.0.5) rooted with magisk 13 by flashing a custom rom, it was in a bootloop after the update.
I tried factory resetting via TWRP because i had a backup ready but the reset somehow failed and my phone rebooted and showed a failed md5 check with these checks failed:
* Cache : Failed
* Boot : Failed
* System : Failed
* Recovery : Failed
* md5 checksum failed
When i try to boot into recovery mode (twrp) it gives me the same message and loops.
Since then i've tried flashing several recovery.img's with several modded and non modded twrp versions, none of them got me into twrp.
I have tried the popular mega unbrick guide from Naman Bhalla twice but didn't help either.
Any ideas on how to fix this?
Thanks in advance
Click to expand...
Click to collapse
You may need to try and flash oxygen OS recovery via adb and then format all your phone , flash oxygen OS and start again from scratch but that's just an educated guess , I'd wait for more responses first just in case someone knows a better method....

Xceeder said:
You may need to try and flash oxygen OS recovery via adb and then format all your phone , flash oxygen OS and start again from scratch but that's just an educated guess , I'd wait for more responses first just in case someone knows a better method....
Click to expand...
Click to collapse
I would say: Jump into fastboot with adb,
make sure you have an img of your old rom, and magisk both in a zip file on your phone
flash the recovery file
install rom
boot
reroot

ODIN Help, phone wont return to stock :(

Hi,
Using latest Odin I am trying to return to my phone to stock but cannot 
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try

Need info on phone model and current firmware and firmwares you are flashing etc

Question How to fix “An error has occured while updating”?

Hello. My problem is:
I’m rooted and on Pixel Experience since September. I’ve had no issues untill my root hiding setup stopped working for some apps. I decided to replace my good ol’ Cygisk Magisk with Magisk Alpha.
When I did “fastboot flash boot boot.img”, it succeeded, but Magisk Manager said that nothing is installed.
I tried installing TWRP via Odin. And this is the breaking point. TWRP TAR archive consists of boot and vbmeta images. So the system and userdata are intact. Odin failed the flash saying something about vbmeta’s hash being incorrect. But instead of properly rebooting my device, it sent it into some pseudo-service mode that says “An error has occured while updating”.
Now this is a clear bug in Odin. I’m 100% certain that my system files are OK. Odin is configured in such a weird way that it sends a device with a fail (it doesn’t care for the exact reason of failure) into that error mode.
How to get out of there without reflashing? I don’t want to lose my perfectly fine-working firmware setup because of some low-paid coder, who thinks that he’s the smartest person on Earth.
I tried flashing blank TAR via Odin to make it reboot my device, but to no avail. Stucks at SetupConnection and crashes itself.