Hello, I had issue flashing my TWRP on device with ADB, device took the command to restart in fastboot mode in bootloader but when I tried to flash twrp it said waiting for device and nothing happened.
I rooted the device using kingroot after twrp flashing failed and wanted to flash twrp using twrp official app, I went into the app and searched for my phone to install the recovery but it wasn't there, only fortuna was there, not gprimeltexx - SM-G530FZ. I downloaded twrp for gprimeltexx from https://dl.twrp.me/gprimeltexx/ in img file, tried to flash it in the app but flash failed notice appeared. TWRP manager forces me to search for the device from the list again and the device is just not there.
Any clue how can I flash TWRP succesfully?
Try flashing the .img.tar file via odin
Related
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Just restore the last stable nandroid you made.
What about fastboot
Steeleio said:
So I took the OTA for MM and everything seemed fine. I noticed that if I tried to go into recovery my device would just restart. I flashed the recovery image but the same thing happened. After I tried to flash the recovery file, ADB did not recoginize my device anymore. I flashed TWRP to see if that would work. From the bootloader ADB did not recognize my device but if I went into TWRP my device showed up. I did not install SuperSU from TWRP but when I rebooted I was in a bootloop. So I used the restore to stock tool to reset everything. It flashed fine but failed on the radio file. Now I can't set it up because it hangs at the WiFi screen, ADB does not recognize the device for me to flash again, and I can't figure out how to fix this.
Click to expand...
Click to collapse
Are you using the new SuperSU beta? The play store / alpha version of supersu is not compatible with MM. I suggest more reading, specifically this thread: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page425
Also, because you did not fastboot flash the LP modem after returning to stock, your radio/wifi will not work. It's not an issue with the phone, but rather user-error. Fortunatally, it is a simple matter of getting you working again.
My advice is: Flash the stock unrooted MM TWRP backup (you should already be on the MM modem) and you should be able to start over. Just be sure to use the appropriate supersu beta, and DO NOT modify the boot image.
I have my op2 with runing with exodus rom. but i think my son playing with the phone deleted twrp, cause i cant enter recovery mode. When I do that my phone simply shows the 1+ logo for the eternity.
Tried with the TWRP manager, selected de TWRP and downloaded, but it gets an error when trying to intall.
Is there a way to re-install the twrp recovery tool?
Via fastboot.
fastboot flash recovery twrpxx.img
What i did stepwise -
1. Unlocked bootloader of my g5 plus
2. Flashed twrp-3.2.3-1-potter.img via adb
3. Booted to TWRP
4. Wiped to decrypt phone
5*. Booted to system to enable usb debugging, enabled it . Transfered magisk , arrow 9.0 rom , gapps to my internal storage of phone
6. Open bootloader , selected recovery mode and got nothing except error "No Command"
So i cannot flashed anything what i wanted to
What and Where i made the mistake ?
How can i get TWRP back?
Thanks all in advance
Solution
1. Flashed magisk17.1 and lazyflasher
2. Updated magisk manager and got root
3. Installed official TWRP app , granted root and downloaded same TWRP.img from which i decrypted the phone.
4. Flashed twrp fom the official twrp app.
5. No irritating No Command error again
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
echo92 said:
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
Click to expand...
Click to collapse
Thanks for your answer sir , but it didn't work
What I did again
1.I flashed same twrp from adb
2. Booted to recovery , but this time TWRP didn't asked password and I could see internal storage in twrp but not on my PC
3*.However I took the whole backup of stock nougat and cross check from restore option as there was backup in TWRP folder. I wanted copy that backup to my PC . But PC cannot detect my phone while in recovery
4. So booted to system and my PC detected my phone but there was no backup in TWRP folder.( But around 6gb(backup) of storage was used but I couldn't see it)
5.Again booted to recovery mode but "No Command" showed again .
I tried several times but I keep losing TWRP and couldn't see the backup which I make
Same problem. Resolved by flashing alternately several times twrp-3.2.1-0-potter.img and twrp-3.2.1-1-potter_persist.img and finally updated twrp-3.2.3-1-potter.img
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
NZedPred said:
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
Click to expand...
Click to collapse
I flashed magisk 17.1 and lazyflasher ,i got magisk and root but cannot install modules may be becoz of f2fs bug . By the way i lost twrp after booting to system again and No command still present in recovery mode . I am frustrated Moto software is just pain in head :silly:
Hi all
I have a question that has probably been asked before but i cant seem to find a definite answer.
I have a Note 3 SM-N9005 (Snapdragon 800 (MSM8974)). I would like to flash latest TWRP. I am sure i have the right TWRP (https://dl.twrp.me/hlte/)
All goes well in Odin but TWRP doesnt boot up. The phone keeps rebooting to the Samsung logo . (FYI i have previously installed latest TWRP on the S3, S4 and S5 along with custom ROMS with not a single problem)
Trying previous versions of TWRP i found the only one that works is twrp-c-hlte-4.4.img.tar, but that is too old to use to flash Android 8.1 or 9.0.
All my searching shows many instructions with a successful installation of TWRP 3.0 or greater on a Note 3. But i cant get that to happen.
Hoping that someone can help with an answer please.
Thanks in advance
Flash it by recovery and not with odin...
Hi
Sorry, Not sure what you mean
Do you mean flash TWRP by going into stock recovery and selecting applying an update from external storage (SD Card)
If so what file type do i need? img or tar?. img i presume
FYI, i am rooted and have tried the following;
*. adb fastboot. (dvice is not recognised in fastboot no matter what drivers i install)
*. Flashify
*. ROM manager
*. ODIN
All flash the latest TWRP (successfully according to the on screen message) but when trying to enter recovery i get a boot loop. Even when i try to boot to the OS, it stays in the recovery boot loop
I recover from the boot loop by re-flashing stock rom (Android 5.0, the latest from Sammobile for my device)
Thanks
turn off auto reboot while flashing twrp in odin (hlte)
Hello,
I am experiencing issues with TWRP on my Samsung SM-J530F. After installing TWRP, my phone is stuck in a bootloop, but I can still boot into TWRP.
The problem is that when I try to install ROMs using ADB or TWRP, my device is detected as just a dot (".") in TWRP, so I cannot proceed with the installation.
I have also tried using ODIN to install a ROM, but it didn't work.
When I tried to use ADB with the "--force" command to sideload the ROM, I received an error message: "adb.exe: sideload requires an argument."
I am looking for a solution to install a compatible ROM on my Samsung SM-J530F.
Edit:Only TWRP Detects my phone as a dot.
nvm it works with orangefox