Related
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Ragarianok said:
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Click to expand...
Click to collapse
I did not do that. I remembered all the steps but forgot that. That is the primary cause of my problem. Anyway to solve it?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
xfstk is the only way. go to following thread and do as suggested. one advice when you get into bootloader. flash raw without AFT. that is best.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Hi,
I don't really know much of rooting and stuff and that is why I have the following problem.
My htc one m8 was rooted for a couple of months but as of yesterday something strange happend.
I really don't know what I did but for the moment my phone is stuck on the boot screen.
By holding power + up + down i can get in the Hboot mode but I have no clue what I can do next.
TWRP is installed and when I try to install a zip in TWRP I have the error of 5DM file missing.
My pc isn't recognizing my phone so I'm really stuck.
Can someone please explain me what I can do? I'm a real noob.
Some extra information, my phone is unlocked, s-on,.. more I don't know.
I would really appreciate it!!!
If you have stock rom and want to have stock too, then you need to flash it by ruu or find an twrp backup for your version.
If you have/want a custom rom then you can easily flash it by twrp, I suggest you updating twrp, then you won't have any issues.
Hi,
I was running LineageOS on my Galaxy Tab S tablet (SM-T800). I tried to update LineageOS. I went into the settings and downloaded the lastest version. However, the installation didn't go through. The download was successful, but an error message told me to try and manually install the update. I tried to go into TWRP mode to install manually the update. Instead of going in the recovery mode, I saw a TWRP app on the Google Play store. I tried and install that app. It went ok, however, I needed to reboot my tablet to finish. I did so, but after that, I got stuck in booting mode, between the TWRP logo and the Samsung logo. So the tablet was trying to boot in TWRP mode, but after about 5 seconds on the splash screen of TWRP, the spalsh screen disapear and then the tablet tries to boot in normal mode. It doesn't work, and the tablet reboots in TWRP mode, but, again, unsuccessful. It's a loop, alterning between the two splash screens.
I tryed to go into download mode and flashed the stock ROM (found on Updato) while using Odin on my computer. It worked. However, after the process, my tablet got stucked on the Samsung logo only. Now, it doesn't go in recovery mode (TWRP). I can only go in download mode or regular mode (but not working). Only the download mode works.
I don't really know waht to do. I tryed to redo the process with Odin and the custon ROM, but it didn't work better.
What can I do?
Thank you very much for your help!
Blaccko said:
Hi,
I was running LineageOS on my Galaxy Tab S tablet (SM-T800). I tried to update LineageOS. I went into the settings and downloaded the lastest version. However, the installation didn't go through. The download was successful, but an error message told me to try and manually install the update. I tried to go into TWRP mode to install manually the update. Instead of going in the recovery mode, I saw a TWRP app on the Google Play store. I tried and install that app. It went ok, however, I needed to reboot my tablet to finish. I did so, but after that, I got stuck in booting mode, between the TWRP logo and the Samsung logo. So the tablet was trying to boot in TWRP mode, but after about 5 seconds on the splash screen of TWRP, the spalsh screen disapear and then the tablet tries to boot in normal mode. It doesn't work, and the tablet reboots in TWRP mode, but, again, unsuccessful. It's a loop, alterning between the two splash screens.
I tryed to go into download mode and flashed the stock ROM (found on Updato) while using Odin on my computer. It worked. However, after the process, my tablet got stucked on the Samsung logo only. Now, it doesn't go in recovery mode (TWRP). I can only go in download mode or regular mode (but not working). Only the download mode works.
I don't really know waht to do. I tryed to redo the process with Odin and the custon ROM, but it didn't work better.
What can I do?
Thank you very much for your help!
Click to expand...
Click to collapse
Have you tried to reflash twrp via odin ? If that works go into twrp reformat your partitions, then flash a custom rom.
Hi,
Thanks for your answer. I tried to reinstall TWRP with Odin on my computer. The process went well, but the reboot of my tablet that occurs at the end of the process got stuck again on the Samsung logo. It didn't get to TWRP mode. I tried to go manually into recovery mode by holding power+vol up+home, but it didn't work.
What else can I try? Thank you,
Blaccko said:
Hi,
Thanks for your answer. I tried to reinstall TWRP with Odin on my computer. The process went well, but the reboot of my tablet that occurs at the end of the process got stuck again on the Samsung logo. It didn't get to TWRP mode. I tried to go manually into recovery mode by holding power+vol up+home, but it didn't work.
What else can I try? Thank you,
Click to expand...
Click to collapse
Are you trying to get to twrp from powered off state ? If not , get to power off state, then use key combo again to try to get into twrp.
Also when you flash twrp, in odi , there is a setting to prevent auto reboot, use that and try to get to twrp via key combo from download. Mode., finally tripple chech the key combo you are using is correct
Hi,
Thanks for the help. I tried to get to TWRP from power off state. The TWRP splash screen appears, and stays on for about 5-10 sec. After that, the splash screen disappear and the tablet reboot to get stuck on the Samsung logo again. It's like if the TWRP booting process doesn't go through...
Thanks again for your help,
Ouch !!
Looks like you got a real problem , and getting into territory I'm not expert in, Ashyx is the real authority with twrp for this device, you can try to pm him and hope he takes pity on you ( he has been helping guys on this qa thread tirelessly for over a year, and is prob taking a well deserved break ).
Otherwise a few more suggestions,
Maybe your PIT is messed up , ( but you prob would not make it to twrp splash screen in that case )
Twrp may still be trying to execute the script from the original linage update and not finding something bails ( total guess ).
Try flashing a stock ( downloaded from sammobile or somwhere you trust ) rom via odin, and see if you can get into the stock recovery. From there do a factory reset and see if you can get stock running.
Try getting into twrp with device connected to pc ( helped in some wierd cases, you never know lol ).
When TWRP splash screen comes up, try some key combos , maybe twrp checks for a script abbort key combo ?
Checkout the TWRP github issues page, see if your bug is there and a solution, create a bug report or mail a dev directly.
Have a look at the TWRP code, maybe some clues ??
Hi,
So not much development here...
I tried to download the stock ROM for my device from Sammobile and tried flashing it with Odin (JOdin actually, I'm on Mac), but it says it need a PIT file. I let Casual fin the PIT file and it finds it. Only, after that my device does not reconnect to Odin even though it's still plugged in my computer. I tried to unplug it then plug it back, but then Odin says the PIT file is corrupted. I tried to restart my device, but still not connecting to Odin...
I tried getting into TWRP with my device connected to my computer. Still the same problem of rebooting while TWRP is booting (while it's on splash page).
No combo key seems to work to keep TWRP open and loading...
Didn't find anything on TWRP github and I'm not saavy enough to look into TWRP code.
So, I'm still stuck with my initial problem. Do any of ou have some advices/suggestions or can help me with my problem please? At this point, I've been without my tablet for more than a month and it S**KS!!
Thanks in advance everyone,
Blaccko said:
Hi,
So not much development here...
I tried to download the stock ROM for my device from Sammobile and tried flashing it with Odin (JOdin actually, I'm on Mac), but it says it need a PIT file. I let Casual fin the PIT file and it finds it. Only, after that my device does not reconnect to Odin even though it's still plugged in my computer. I tried to unplug it then plug it back, but then Odin says the PIT file is corrupted. I tried to restart my device, but still not connecting to Odin...
I tried getting into TWRP with my device connected to my computer. Still the same problem of rebooting while TWRP is booting (while it's on splash page).
No combo key seems to work to keep TWRP open and loading...
Didn't find anything on TWRP github and I'm not saavy enough to look into TWRP code.
So, I'm still stuck with my initial problem. Do any of ou have some advices/suggestions or can help me with my problem please? At this point, I've been without my tablet for more than a month and it S**KS!!
Thanks in advance everyone,
Click to expand...
Click to collapse
Use ODIN via Windows or a VM on your Mac.
Flash stock firmware then boot to recovery and factory reset.
Reboot and wait ten minutes.
Hi, thanks a lot for your time.
I will try that at work tomorrow as I don't have Windows at home. However, I did try to flash stock ROM with Windows initially (see first post for more info) and it didn't solve my problem. I wasn't able to access recovery mode after the stock ROM was flashed. Hope it's gonna work now and I'll be able to factory reset.
I'll let you know tomorrow afternoon.
Thanks,
ashyx said:
Use ODIN via Windows or a VM on your Mac.
Flash stock firmware then boot to recovery and factory reset.
Reboot and wait ten minutes.
Click to expand...
Click to collapse
WOW!!! Thank you so much Ashyx. I can now finally use my Tab S. I'm so grateful!!! Thousand time thank you! I deeply appreciate your help for resolving my problem.
ashyx said:
Use ODIN via Windows or a VM on your Mac.
Flash stock firmware then boot to recovery and factory reset.
Reboot and wait ten minutes.
Click to expand...
Click to collapse
HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler
Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom
Tsuragi said:
Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom
Click to expand...
Click to collapse
Thanks Tsuragi,
Forgot about that - it was me who posted that solution some time ago duh!
Pootler
pootler said:
HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler
Click to expand...
Click to collapse
Hey bro same experience, thats why im stock in android 10 with unlock bootloader. but i successfully flashed lineage with unofficial twrp but the problem is i cant flashed gapps thats why i cant install pre apps and cant use the default message and call. please help me