I was using lineage 18.1 on my galaxy S10e and I had some problems with the rom. I had just installed it and many apps were acting weird. So i decided to change roms, but everything I flashed was giving me a "No os" error when trying to reboot with TWRP. Now not even the Lineage 18.1 I was using before is working. While in TWRP my computer does not open MTP, even though it' s enabled.
In download mode (fastboot) I can't use odin because it doen't recognize my phone (tried with different odin versions too). Heimdall recognizes the device but get's stuck on "Initializing protocol".
In TWRP mode it doenst matter what I flash, it gives a No OS error and I get stuck in a bootloop. I've already tried installing roms with ADB Sideload and using a flashdrive/OTG.
What I already tried:
Reinstalling drivers with zadig.
Installing samsung mtp drivers.
Other usb cable and port.
Plugging another samsung device to computer (also does not recognize).
It seems I have a problem both with the computer and the phone. The computer (file explorer and odin) does not recognize locked device with stock rom and my bricked S10e, though heimdall and SDB sideload recognize the devices. And the phone, even though I can sideload and install from USB/OTG, I get No OS error and get stuck in a bootloop.
Odin versions: 3.13.3 and 3.14.1
Heimdall version: 1.4.0
Phones: Samsung Galaxy S10e (bricked) and Samsung Galaxy S9 (locked/stock)
ROMs tried: Lineage 18.1/19 and Pixel Experience.
P.S.: I followed every install instruction from scratch multiple times.
Edit: After rebooting my phone a few times, something happened and I can access internal storage again.
Edit 2: For some reason the problem was with using TWRP to install roms. I was able to use TWRP to install Lineage Recoery, and from there, everything worked perfectly. I wiped everything, installed lineage 18.1 official, open gapps and magisk, without rebooting. Then, I was able to boot normally.
Related
Totally n00bed my Nexus S.
Was running the latest Miui and installed ROM Manager. Decided to download stock Android and install.
Now the phone is boot-looped (stuck on the Nexus boot image) and Recovery seems to be gone.
I tried pushing the recovery image file but adb won't detect the device.
Any advice?
I had that once when I installed stock. I fixed it by going into recovery and clearing cache and dalvik
Sent from my Nexus S using XDA App
I can't boot into recovery though - It's missing.
theadb said:
Totally n00bed my Nexus S.
Was running the latest Miui and installed ROM Manager. Decided to download stock Android and install.
Now the phone is boot-looped (stuck on the Nexus boot image) and Recovery seems to be gone.
I tried pushing the recovery image file but adb won't detect the device.
Any advice?
Click to expand...
Click to collapse
you need to install the proper nexus s drivers.easiest way is to go to the pdanet website http://junefabrics.com/android/ , download their free product, and let it install the drivers for you. did you flash the recovery through rom manager originally? anyways, then wipe(data. factory reset) and reflash the stock rom. you always have to wipe before flashing a DIFFERENT rom, or youll get stuck in a bootloop.
I installed the 64-bit drivers from PDA already but I'm running XP 64-bit (could that be the issue?)
theadb said:
I installed the 64-bit drivers from PDA already but I'm running XP 64-bit (could that be the issue?)
Click to expand...
Click to collapse
maybe?????
Will adb still work even though I can't boot my phone and turn usb debugging on?
Unfortunately I have 64-bit windows at work, but I'll try on my Win7 or Mac at home.
Still can't get adb to or fastboot to recognize the device...maybe I'm missing something...
I have no recovery and can't boot - what can I do?
Bump. In the exact same mess.
I was on MIUI ICS and tried to go to a stock GB rom, ended up stuck at the boot animation in the fresh rom (which kept looping). Recovery was a no-go too. I tried using adb to push another stock rom which again, installed but got stuck at the boot animation. After that even adb stopped detecting the phone.
What do I do now? theadb how did you fix it?
ADB is working as I plugged in my HD2, which was detected immediately.
Er bump?
Use fastboot to flash a new recovery, then boot into recovery and do what is needed. Recovery will probably be replaced by stock each time you attempt to boot into android while the stock ROM is installed.
I'm in the exact same situation and I don't really think there's anything we can do. We can't enter fastboot. We can't go into download mode. We can't boot into recovery there is literally zilch that we can do to fix the phone.
HAYLP! I've got a rooted my Note 10.1 2014 edition and had loads of different Roms installed with no issues at all. Last night (whilst slightly worse for wear from excessive Vodka it has to be said) I tried to another custom ROM from XDA. http://forum.xda-developers.com/gal...opment/rom-note-s-10-1-2014-rom-beta-t2859040
I'm not sure what happened, it appeared to install fine after a full wipe, device rebooted then was stuck on the Samsung logo for ages (I know ROMS take a long time on 1st boot but I'm talking 3hrs+ looking at the Samsung logo boot screen.)
So I figured I'd power off and just manually flash another ROM but I can't get either USB OTG to work after flashing TWRP via ODIN (tried 2.84 thru 2.87) the option just isn't there to mount USB storage - tried 2 different sticks in FAT32 and ExFAT, nada.
Tried ADB but get a device not found from either download mode or ADB sideload in TWRP.
As the device shows up in ODIN, I figured I'd flash a ROM via that but I can't seem to find any ODIN flashable roms for the SM-P600. It was running Temasek's CM 12.1 5.1.1 rom with the 5.1.1 Bootloader.
I've tried reflashing the Stock Firmware and also as a last ditch effort, using the Stock PIT file to repoartition but it's still just sitting on the Samsung Logo forever.
Is there a separate CSC / Bootloader that I'm missing or something? (Or is it possible to just reflash Temesek or another Rom in Odin somehow?)
Anyone got any ideas please?
mpthreeuk said:
HAYLP! I've got a rooted my Note 10.1 2014 edition and had loads of different Roms installed with no issues at all. Last night (whilst slightly worse for wear from excessive Vodka it has to be said) I tried to another custom ROM from XDA. http://forum.xda-developers.com/gal...opment/rom-note-s-10-1-2014-rom-beta-t2859040
I'm not sure what happened, it appeared to install fine after a full wipe, device rebooted then was stuck on the Samsung logo for ages (I know ROMS take a long time on 1st boot but I'm talking 3hrs+ looking at the Samsung logo boot screen.)
So I figured I'd power off and just manually flash another ROM but I can't get either USB OTG to work after flashing TWRP via ODIN (tried 2.84 thru 2.87) the option just isn't there to mount USB storage - tried 2 different sticks in FAT32 and ExFAT, nada.
Tried ADB but get a device not found from either download mode or ADB sideload in TWRP.
As the device shows up in ODIN, I figured I'd flash a ROM via that but I can't seem to find any ODIN flashable roms for the SM-P600. It was running Temasek's CM 12.1 5.1.1 rom with the 5.1.1 Bootloader.
I've tried reflashing the Stock Firmware and also as a last ditch effort, using the Stock PIT file to repoartition but it's still just sitting on the Samsung Logo forever.
Is there a separate CSC / Bootloader that I'm missing or something? (Or is it possible to just reflash Temesek or another Rom in Odin somehow?)
Anyone got any ideas please?
Click to expand...
Click to collapse
Hi,
Try posting your question here:
http://forum.xda-developers.com/galaxy-note-10-2014/help
The experts there may be able to help.
Good luck!
Hello everyone!
I am new here and really looking forward for some answers. I own oneplus one and had a good experience with it. I had upgraded to custom rom that is lineage os 14.1
I wanted to upgrade it to 15.1 through Twrp. I followed the same procedure as i did for last flashing. I wiped the old data and everything and started to flash new rom. But this time twrp was giving an error. When I did research on that i found that i needed to upgrade to newer version of twrp to install lineage os 15.1
I did the same. And then end of it I just unselected the Supersu root and it reboots. Now when I go to the twrp recovery. The oneplus icon shows but then nothing happens. My phone now doesn't have a rom and twrp recovery won't open. When I connect it to my laptop through fastboot, cmd doesn't recognizes the device. I don't have any knowledge about tech and stuff. And I might have done something wrong. Please help me with some solutions
First of all, try to reinstall TWRP trough fastboot (boot in bootloader mode with Volume UP + power), just google a guide if you don't know how fastboot works. also be sure to use the correct twrp for bacon
After that you should be able to boot back in recovery and flash your rom
if still it doesn't work, follow this guide
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sometimes it happens we brick our phones but No worries as long as you can go to fastboot you can always restore back to how it was before.
Either use the Program the guy above provided or this guide:
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I want to know how to flash the twrp again through fastboot, because when I connect it, phone is not detected in cmd. It says no fastboot devices are there. But then I checked and it says some android thing is connected in device manager. I hope it is my Oneplus one. How to pass this step?
It's the android drivers. Make sure you have the drivers installed.
Thank you so much. I was able to download the twrp again and flashed the 14.1 lineage os. The latest twrp is not flashing in the phone i don't know why and because of that 15.1 lineage os is not flashing and shows error. But still it's a relief that my phone is working. Also, when i switch on the camera it's not working and the flashlight icon also is dim and doesn't gets clicked and not works.
So I have a device which was rooted then they tried to update it. Now it's stuck in a TWRP loop which wouldn't be that bad if the only usable stock ROM wasn't for SPF.
SPF requires a shut down phone but TWRP keeps on booting the phone up when I connect it to the pc. Any ideas how this could be solved?
Or anyone knows how to make a SPF firmware into a TWRP compatible zip?
(Current Nikoa 3 Stock I tried to use: https://mega.nz/#!FMpHVYpZ!mNVx6Ifr6z6YpslP-F4kLBs1ldfuiZEiZOjQATgORWg (it's in one of the other forum posts)).
Or maybe make do something with adb sideload to install?
I tried shutting the phone down from adb, still reboots. I don't know if removing the battery would solve it, but that quite hard to do.
Please help. This stubborn TWPR annoys the ** out of me.
TWPR version: v3.1.0 by Sajal
Guide used for rooting: https://forum.xda-developers.com/nokia-3/how-to/guide-unlock-bootloader-root-flash-twrp-t3726649
Ok so i did the following in this order.
Installed twrp 3.3.1.0 via odin which worked perfectly.
Installed lineage os 17.1.
Installed no verify.
Installed gapps.
Had it all up ad running perfectly fine for a few weeks.
I decided to try a different os called pixel experience which i also got running just fine.
However i didn't like it and decided to go back to lineage os.
I used the exactly the same steps i used previously to wipe the system os inside twrp.
however when i tried to wipe the data it failed and then my phone auto rebooted and now i can't do anything.
It wont charge so needs to be plugged in to even turn on.
Once its plugged in it auto boots to a twrp splash screen and is stuck there and cant get into the twrp menu do install an os.
I can get into the download mode and odin detects the phone so i tried reinstalling twrp which says it was successful but when i reboot it gets stuck in the same splash screen.
i also tried reinstalling the original bl ap cp csc files that i had previously had installed which after many attempts finally go them to install but still loads the twrp splash screen and gets stuck there.
ive tried using adb fastboot loader using cmd but it doesn't detect the device so cant do any that way at all
i fear my phone is completely bricked and unusable please if you can offer any help would be much appreciated as im at the point where im looking to buy another phone as this is my old phone atm.
HI
Can't you come back to the last official firm for our S7 ?
It is an Oreo 8.0.0 firm
Have a look at samfirm ( or updato) and search for GF930FXXS8ETC2_xxx.zip
U flash that with Odin ( 3.13.1 I think) and yr phone is back to life !!!
Hope this helps