Develop Bugs

[FIXED] Unbrick ZE551ML without computer

Hello!
I made an OTA update while rooted so I soft bricked my phone lol
I dont have access to a computer for some weeks so I'd like to know how I could flash a stock ROM using an Android tablet (Samsung Galaxy Tab Pro 10.1")
I installed ADB and Fastboot by following this thread http://forum.xda-developers.com/showthread.php?t=2586472&page=1 but I apparently need 1.0.32 version of ADB and I can't find any guide to install it on an Android Device, plus when I use a Fastboot command the terminal emulator sticks on 'Waiting for device'
My Device does appear when I use 'adb devices' but it doesn't when I use 'fastboot devices'
I really need help guys
Thank you very much for reading this

Ok, you can follow this, but i'm not sure if it works:
1. Download the OTA package from Asus.
2. Rename it to mofd_sdupdate.zip.
3. Push that file to the root of your phone internal storage (/sdcard/mofd_sdupdate.zip) not anywhere else.
4. Reboot to recovery, it will flash the update automatically
5. Reboot your phone normally.
6. If it bootloops, try hold the power button to turn it off, then turn it on again.
7. If it still bootloop, wipe /cache in recovery, then reboot
8. If it still bootloop, wipe /data in recovery, then reboot
9. If still bootloop, do step 6
10. If it still loops, I have no idea . Try using a computer.
ELSE, enjoy the new update.
If in 5 min it doesn't show "Android is upgrading" it means that it fell into a bootloop

HungNgocPhat said:
Ok, you can follow this, but i'm not sure if it works:
1. Download the OTA package from Asus.
2. Rename it to mofd_sdupdate.zip.
3. Push that file to the root of your phone internal storage (/sdcard/mofd_sdupdate.zip) not anywhere else.
4. Reboot to recovery, it will flash the update automatically
5. Reboot your phone normally.
6. If it bootloops, try hold the power button to turn it off, then turn it on again.
7. If it still bootloop, wipe /cache in recovery, then reboot
8. If it still bootloop, wipe /data in recovery, then reboot
9. If still bootloop, do step 6
10. If it still loops, I have no idea . Try using a computer.
ELSE, enjoy the new update.
If in 5 min it doesn't show "Android is upgrading" it means that it fell into a bootloop
Click to expand...
Click to collapse
Thank you very much

HungNgocPhat said:
Ok, you can follow this, but i'm not sure if it works:
1. Download the OTA package from Asus.
2. Rename it to mofd_sdupdate.zip.
3. Push that file to the root of your phone internal storage (/sdcard/mofd_sdupdate.zip) not anywhere else.
4. Reboot to recovery, it will flash the update automatically
5. Reboot your phone normally.
6. If it bootloops, try hold the power button to turn it off, then turn it on again.
7. If it still bootloop, wipe /cache in recovery, then reboot
8. If it still bootloop, wipe /data in recovery, then reboot
9. If still bootloop, do step 6
10. If it still loops, I have no idea . Try using a computer.
ELSE, enjoy the new update.
If in 5 min it doesn't show "Android is upgrading" it means that it fell into a bootloop
Click to expand...
Click to collapse
How can I push the file? :/

I fixed the problem!
This is how I did it:
I downloaded last WW OTA Update from Asus site for my phone
I renamed it mofd_sdupdate
I've put it on a SD CARD
I inserted SD CARD in the phone and the update started alone, after it my phone was saved

Op3 only boots into twrp after failed update

Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...

I have the same problem

Here the same but with CM14 after a wrong download & install now Recovery Loop
How to solve???

I had this problem too. Flash the Oxygen recovery OB7. It will update automatically and turn on. But be patient because it takes a lot.

sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
The way I found works is to start from scratch and yes you will lose all data on the phone. Had to do this yesterday because I messed a few things up.
Make sure you have the modified recovery (1.28), Beta 9 Full (1.3GB), and SuperSU (SR5) if you want root, on your computer. And you will need your computer for these steps.
1. Boot to TWRP > Wipe > Format Data. There's a warning screen you just type yes and press enter. This should set your /data partition to F2FS; all other partitions will remain EXT4. (The TWRP MTP didn't pop up on me so then I had to reflash twrp from fastboot). If your PC see's your device after this step, skip to step 9, but my guess is, when you format data, the required files for MTP disappears with it.
2. Power off your device.
3. Put device into fastboot mode (start device by holding volume up + power)
4. Connect device to PC.
5. fastboot flash recovery modded_twrp.img
6. Disconnect device from computer and shut down phone.
7. Load recovery (start device by holding volume down + power)
8. Connect to PC
9. TWRP MTP should be working; transfer the recovery file, beta9, and super SU (if you want root) to your internal storage.
10. I usually disconnect my phone from my PC at this point.
11. Go to Install > sdcard > media folder (your files should be here).
12. Flash Beta 9 zip.
13. Reflash modded TWRP (click Install Image button and you should see your TWRP file).
14. Reboot to Recovery (I noticed that click on Reboot and Recovery freezes TWRP on me, so you can manually power down by holding power button down).
15. Swipe to accept modifications
16. If you don't need root, you're all done. The first boot takes like 5 min.
For some reason for root, it doesn't work if you try without freeing up some space in the system folder. What you can do is:
1. In TWRP > Mount > tick off System > head back out to main menu
18. Advanced > File Manager > > system folder > app folder > and delete some google apps (ie. calendar, gmail, chrome; should be enough; can be downloaded from play store later)
19. Flash SuperSU SR5.
20. Wipe Cache and Dalvik, reboot.
I've noticed that if you don't root, your device will be encrypted on first boot of beta 9 (which causes some issues in TWRP not being able to mount the /data partition and decryption passwords not working in TWRP.

Same problem here, **** broken OB9 update.
EDIT: For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.

I used twrp-3.0.2-22 to reflash beta 9 all is well.
I have same problem with twrp-3.0.2-1.28. Just boot into bootloader and flash twrp-3.0.2-22.

Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.

No need for clean installation like hw4ng3r said.
I'll copy my other post's edit here if someone needs it.
For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
Click to expand...
Click to collapse
Got 145849 AnTuTu result with OB9. Might be able to get a better result if I were to clean install, but I've just dirty flashed every update since 3.2.5.

karliyo said:
No need for clean installation like hw4ng3r said.
Click to expand...
Click to collapse
Very true.
I interpreted the OP's comment as:
1. Already on TWRP
2. Tried full wipe and install (all data lost anyways)
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
Tumpster said:
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
Click to expand...
Click to collapse
I've read that .22 TWRP doesn't have decryption issues of the /data partition like .28 has, but don't take my word for it. And the encryption happened to me when I flashed Beta9 from TWRP .28 and rebooted system without flashing Super SU.
The decryption of the /data partition in TWRP seems to be an issue if the file system is F2FS on Beta 8 and Beta 9. I haven't had any issues with EXT4.

sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
Download stock recovery from OnePlus site (on very bottom) ,flash it using fastboot and than sideload new beta 9

Previous Root on Stock + TWRP + Magisk + OTA update needed + Stupidity + Sultan

OK, so I've been getting the August OTA nagging for a bit, and I finally decided I needed to read some instructions on things and get it on my already rooted phone.
I started with...
1. Unlocked bootloader
2. Root on the stock ROM
3. TWRP 3.3.0-0 recovery installed
4. Magisk 19.3 (19300) installed
5. Windows installed platform tools/drivers/etc
What I did...
1. Downloaded the factory image
2. Removed the "-w" from the fastboot update image line in the batch file
3. Ran that batch file... the 1st bootloader bit went fine, but the reboot seemed to not reconnect the phone via usb
4. Unplugging the usb and replugging it successfully seemed to trigger the 2nd radio update bit, and again the reboot left the batch file hanging
5. Unplugged and replugged and the final fastboot update for the image fails saying something about memory (I didn't save what was on screen because CMD.exe closed when I pressed a key).
6. I try to reboot and it gets in a boot loop. Bootloader unlocked screen to all white G screen and back again.
I figured I'm screwed. Might as well give up and do the Sultan ROM...
7. Launch recovery and get into TWRP
8. ADB Push the most recent Sultan Kernel to the phone from my PC
9. Flash Sultan in TWRP
10. Flash TWRP in TWRP
11. Flash Magisk in TWRP
12. Reboot
And here I am looking at my original setup, with all my apps and data. I still have root. No August patch installed, but my Kernel is 4.4.169-Sultan. So....
I have so many questions.
What went wrong?
What went right?
Sultan doesn't seem any different at all... is that part not right?
What do I do now?

boneriffic said:
What do I do now?
Click to expand...
Click to collapse
You can try using a different cable or USB port to see if that takes care of the flashing issue. Sometimes that's all it takes.
I would also double check your fastboot/adb files to make sure they are the latest from Google.

Pixel Experience boot loop + string of stupid decisions: is there any way out?

Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!

mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.

Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps

mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.

Samsung A3 (2017) Install Custom ROM without Home button

Hi guys,
I have a Samsung A3 (2017) and my home button does not work any more, which is not a problem for me.
My goal is to install LineageOS.
Here is what I tried:
- Install ADB on my windows PC
- Install USB drivers
- Reboot into download mode via adb reboot download
- flash TWRP
That's where the problem comes into play, because I don't see any option to get into recovery mode directly from download mode (without the home button). But if I let the phone boot normally first, to be able to use adb reboot recovery, the TWRP will be overwritten by stock recovery, so I never actually see TWRP...
Doe you know any other way?
Thanks for all your great work here.
seb

Nobody has an idea?
For rooting (no custom ROM), I also always need custom recovery for which I need the physical home button, right?
So sad, don't want to buy a new phone, I like this one. But would need root or a custom ROM to free up space...