By InstanceDeveloper


2019-05-16 12:18:10 8 Comments

I've tried to upgrade the rom in MOTO G4 Plus using TWRP version of 3.2.1.0 and during installation process I wiped out the existing android 7.0.1 without backup(understood the cost of backups now). As I faced error while installing android 9.0.1 with error 255 code because of TWRP some upgrade issue couldn't complete the installation process successfully.

I tried multiple ways to upgrade TWRP which was not successful and even fastboot commands aren't working now. Whenever I try fastboot + combinational command like devices and etc it goes into an infinite loop with an error code iterator not found. After a good amount of search found about ADB and happily can connect to my device using ADB now. Then started trying with multiple options like adb side load after reading multiple forum answers and posts I did pushed a rom to scared/data/media after reading this forum NEED HELP: Accidentally deleted OS in TWRP/Cant install Rom which was successfully pushed but didn't do any thing nor I couldn't understand what to do after pushing it.

Then started search again to install stock rom in any different ways before coming here and stumbled at this question which is similar did read the question and included forum post in it to go start the process when I did download stock rom stock rom download couldn't find any flashall.sh file to start the process

Now I'm stuck and couldn't find better place to find a working solution for this situation. Can somebody help me? What can I do while my phone is in this state?

1 comments

@InstanceDeveloper 2019-05-16 23:25:22

Here is the Full Forum discussion link to the problem I've faced. Thanks everyone who tried to help me out.

For Quick Solution follow this steps mentioned below:

  1. If you still have access to TWRP on your device? please push 32bit flashable ROM to your device.
  2. Try with a TWRP flashable like the stock ROM Oreo flashable https://forum.xda-developers.com/mot...-test-t3873367 and follow the instructions to install it (i.e. push to your device, or copy to an SD card, then tap install in TWRP to flash it to your device). This TWRP flashable should work on this mentioned TWRP version since it's 32 bit.
  3. The stock ROM download would still require fastboot, so I'm not sure why the fastboot is not working and not choosing the fastboot method as of now.

FYI: error 255 when flashing custom Oreo or Pie ROMs means that the TWRP is 32 bit, whereas the custom ROM requires a 64 bit TWRP.

@Firelord 2019-05-17 09:17:04

It is best if you mention the details behind that link because this answer would lose its usefulness should the link expires.

Related Questions

Sponsored Content

1 Answered Questions

How to install TWRP after Magisk?

  • 2018-09-27 15:01:14
  • Abraham Murciano Benzadon
  • 1081 View
  • 0 Score
  • 1 Answer
  • Tags:   twrp magisk oneplus-6

1 Answered Questions

Booting android using 'fastboot boot'

  • 2017-11-13 19:55:29
  • kuruczgyurci
  • 2174 View
  • 1 Score
  • 1 Answer
  • Tags:   boot fastboot

1 Answered Questions

[SOLVED] Nextbit robin recognised on fastboot but not adb shell

  • 2018-12-14 12:36:10
  • Jon
  • 50 View
  • 1 Score
  • 1 Answer
  • Tags:   adb fastboot

1 Answered Questions

[SOLVED] Restoring /system but not /data within TWRP

  • 2018-10-24 21:39:39
  • EinderJam
  • 956 View
  • 0 Score
  • 1 Answer
  • Tags:   twrp restore

1 Answered Questions

Bootloop and inaccessible to fastboot /adb

2 Answered Questions

2 Answered Questions

[SOLVED] FASTBOOT commands don't work at all on my Samsung phone

  • 2017-12-07 10:14:57
  • Amin
  • 1576 View
  • 0 Score
  • 2 Answer
  • Tags:   samsung fastboot

1 Answered Questions

0 Answered Questions

LG G2 "Fastboot mode started"

1 Answered Questions

Sponsored Content