I was just brought a phone that's stuck at a screen with a red exclamation point in a triangle. He said he had installed the latest version of TWRP and was trying to install Xposed from recovery. At one point it was stuck booting in to TWRP recovery and after some messing around he got it stuck on the stock recovery screen. He brought it to me and now we can't get it to do anything - doesn't show up in adb or fastboot devices and can't turn it off. I have no idea what to do...?
Edit: Well, just sitting there on the desk it suddenly rebooted in to TWRP on its own. Still stuck booting in to TWRP now.
Trying holding power and volume up at same time, as soon as it shuts down switch to holding power and volume down helpfully that will get you to boot loader
HTC One (M8)
Ok, I'm lost now. We got it in to fastboot and flashed CWM to the recovery partition. Now, if it reboots in to recovery, we see CWM, and if we try to reboot to system it opens TWRP. Did he flash TWRP to the wrong partition or something? What do I do from here?
qoncept said:
Ok, I'm lost now. We got it in to fastboot and flashed CWM to the recovery partition. Now, if it reboots in to recovery, we see CWM, and if we try to reboot to system it opens TWRP. Did he flash TWRP to the wrong partition or something? What do I do from here?
Click to expand...
Click to collapse
sounds like system is wiped flash a rom
Grr, androidfilehost.com is blocked at work and I can't find a single rom anywhere else. He swears there's no way he could have wiped system -- is there anything else that could be wrong?
qoncept said:
Grr, androidfilehost.com is blocked at work and I can't find a single rom anywhere else. He swears there's no way he could have wiped system -- is there anything else that could be wrong?
Click to expand...
Click to collapse
he did something he shouldnt have
i dont think its anything else other then maybe a bad rom flash or like you said flash recovery to wrong partition i dunno, if you boot to system and it doesn't boot system thats a good sign there is no system to boot to
try this its not on androidfilehost,
http://goo.im/devs/Turge/ViperOneM8/ViperOneM8_1.3.0.zip
http://www.ab-ed.de/baadnewz/m8/insertcoin_sense6_m8-2.3.2.zip
qoncept said:
Grr, androidfilehost.com is blocked at work and I can't find a single rom anywhere else. He swears there's no way he could have wiped system -- is there anything else that could be wrong?
Click to expand...
Click to collapse
Sounds to me like TWRP got flashed to the "boot" partition. That's why you were able to flash CWM (presumably correctly), then "reboot system" from CWM but instead go into TWRP. Now that you have a recovery in the "recovery" partition you just need to flash a ROM within CWM and you'll be good to go.
I heard that the TWRP abd terminal instruction on their website are wrong and will cause this problem (flashing recovery to the "boot" partition). I always flash recoveries (and boot.img's for my other s-on devices)) via fastboot since I can easily understand the syntax.
Fastboot flash <partition> <filename>
Alright, it looks like he tried to flash a bad zip like you guys say. He wants a stock rom - can I use the stock RUU without wiping data or is he going to end up with a fresh phone no matter what?
qoncept said:
Alright, it looks like he tried to flash a bad zip like you guys say. He wants a stock rom - can I use the stock RUU without wiping data or is he going to end up with a fresh phone no matter what?
Click to expand...
Click to collapse
he can use RUU, he can use this stock rom
http://forum.xda-developers.com/showthread.php?t=2722699 (but it hosted at androidfile)
these are stock'ish( these arent androidfile)
http://forum.xda-developers.com/showthread.php?t=2727300
http://forum.xda-developers.com/showthread.php?t=2722927
Sigh.. I'm getting this when I try to flash the RUU:
Code:
C:\phone\Data>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (1572932 KB)...
OKAY [ 47.228s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 47.237s
Edit: Same with all other zips.
qoncept said:
Sigh.. I'm getting this when I try to flash the RUU:
Code:
C:\phone\Data>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (1572932 KB)...
OKAY [ 47.228s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 47.237s
Edit: Same with all other zips.
Click to expand...
Click to collapse
Since you can get into recovery (pretty sure CWM is the recovery properly installed in this case) you should just download a ROM and put it on the phone's SD Card (always check md5) and install it through CWM. If he wants stock, at least give him a pretty stock ROM like one from here:
http://forum.xda-developers.com/showthread.php?t=2708291
Keep the command line stuff to a minimum and use the GUI of the recovery, that's why they're there.
Ok, I got that BoneStock rom installed. BlinkFeed is crashing occasionally (he's using a different launcher) which is annoying but at least it works. Is there a way to get back to the stock rom from this? What will happen if he tries to do a software update?
Could I flash this?
qoncept said:
Ok, I got that BoneStock rom installed. BlinkFeed is crashing occasionally (he's using a different launcher) which is annoying but at least it works. Is there a way to get back to the stock rom from this? What will happen if he tries to do a software update?
Click to expand...
Click to collapse
If you really insist on a true stock, unrooted phone, I'd say your easiest options are either the RUU'ish option you seem to have already tried or you could look to the nandroid someone posted in this forum of his stock setup.
http://forum.xda-developers.com/showthread.php?t=2725001
Note that the nandroid was made with TWRP so you'll have to replace your CWM with TWRP (hopefully correctly this time )
Personally, I'm a fan so far of the ViperOne ROM while I'm waiting for a stable AOSP ROM. That's entirely up to you though.
cntryby429 said:
If you really insist on a true stock, unrooted phone, I'd say your easiest options are either the RUU'ish option you seem to have already tried or you could look to the nandroid someone posted in this forum of his stock setup.
http://forum.xda-developers.com/showthread.php?t=2725001
Note that the nandroid was made with TWRP so you'll have to replace your CWM with TWRP (hopefully correctly this time )
Personally, I'm a fan so far of the ViperOne ROM while I'm waiting for a stable AOSP ROM. That's entirely up to you though.
Click to expand...
Click to collapse
He just wants to get it back to bone stock so when he goes and tries again he knows what he's dealing with. It looks like restoring the system partition from that nandroid backup did it. Thanks a lot for your help!
Related
Hi all, I've been trying for the past 8 hours(you can imagine how frustrated i am right now) to install HatkaXL(http://forum.xda-developers.com/showthread.php?t=2075783) for so long now and I have literally no idea where to go. I was only just trying to switch from cleanrom to Hatka. And I've ended up with absolutely no progress since 8 hours have passed. Actually, i've probably lost progress because i accidentally wiped my data without backing up. Here's what i've done so far:
i'm under AT&T, hboot-1.14, any other info i'll be glad to share. it's rooted and currently unlocked of course.
1. Used fastboot flash boot boot.img to no avail
2. Re-locked bootloader, ran an RUU(i made sure it was compatible), unlocked it and tried to flash HatkaXL froma fresh start
3. Wiped data, cache, etc. then flashed the rom(which still didnt work)
4. flashed TWRP, rebooted, went into TWRP, wiped data, cache, etc. and then flashed HatkaXL
What the problem is that my one x won't go past the HTC screen with all that red developmental font. It'll boot and then go to the screen, stay there for about 10 seconds and then turn off. Then it'll start up again 10 seconds later to boot back to TWRP.
At one point, i encountered a boot loop where it actually went past the red developmental font screen and to the HTCtm Beats Audio and then it just restarted from there. However, now that issue disappeared and it's just booting to recovery after shutting down.
Now that's where I was thinking that maybe since it's booting directly to TWRP that would mean that I would have to go into cmd and 'fastboot flash boot boot.img' right? I did exactly that, one, twice, three times, even with fastboot erase cache.
i can't even remeber everything i did because i'm so tired since i've been up through the night reading throug threads, trying to fix this damn thing.
I would really really appreciate it if anyone could help me out here because i've never been this lost when it came to technology lol.
It sounds like you were on the right track, I am lost why it failed for you?
Can you install cleanrom again? eg is it just HatkaXl that is not working? Perhaps your download is bad or the ROM is simply broken and you need to report it to the dev?
When you were flashing the boot.img did it say success? Did you triple check you are extracting the correct boot.img to the correct folder?
Just to be clear to install ROM's I often do:
1)wipe data and system
2)install ROM
3)fastboot flash boot boot.img
twistedddx said:
It sounds like you were on the right track, I am lost why it failed for you?
Can you install cleanrom again? eg is it just HatkaXl that is not working? Perhaps your download is bad or the ROM is simply broken and you need to report it to the dev?
When you were flashing the boot.img did it say success? Did you triple check you are extracting the correct boot.img to the correct folder?
Just to be clear to install ROM's I often do:
1)wipe data and system
2)install ROM
3)fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks for the response. Yep, every time i flash the boot.img, it's always a success. i also mae sure it's the correct one.
sending 'boot' (6156 KB)...
OKAY [ 0.933s]
writing 'boot'...
OKAY [ 1.475s]
finished. total time: 2.413s
Click to expand...
Click to collapse
I just tried to install cleanrom 5.1 again and it's not working either. Actually, it's stuck at the red developmental font screen this time so atleast it's not immediately rebooting to go to TWRP.
UPDATE: It's working! CleanROM! Thank you so much man! I'll be back to ask you another question. Gotta go real quick.
Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen
a box of kittens said:
Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen
Click to expand...
Click to collapse
I also noticed this. Op, a few things to remember when flashing boot.img.
The boot.img needs to be extracted from the rom you are flashing.
The phone must be in bootloader, plugged in to pc and in fastboot usb mode. (the phone will say fastboot usb.
The boot.img must be in the folder with the fast boot and adb programs.
I have more than just a feeling you were doing something wrong
Sent from my One X using xda app-developers app
Thanks for the responses guys, you guys are saving me lots of stress and time.
a box of kittens said:
Correct me if I'm wrong but clean Rom 5.1 flashes the boot img for you I didn't see you flashing the boot.img the other times successfully so yes it won't get past that HTC screen
Click to expand...
Click to collapse
You are correct that clean rom 5.1 flashes it for you, which is through its AROMA installer. However, HatkaXL also uses the AROMA installer, and there's a line in the installation screen where it says "flashing boot.img." - both ROMs have that line. Interestingly, it worked when I followed twistedddx's order so I'm going to try that again.
exad said:
I also noticed this. Op, a few things to remember when flashing boot.img.
The boot.img needs to be extracted from the rom you are flashing.
The phone must be in bootloader, plugged in to pc and in fastboot usb mode. (the phone will say fastboot usb.
The boot.img must be in the folder with the fast boot and adb programs.
I have more than just a feeling you were doing something wrong
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yup, I have those in the same folder correctly. I always extract the boot.img from the rom zip into the folder with both fastboot and adb(how else would I able to have fastbooted in the first place?), always made sure the phone was in bootloader, plugged in, and in fastboot usb.
edit: I wiped, then installed hatkaXL, then fastboot flash boot boot.img, and now it starts, it gets past the red developmental screen, INTO the HTC Onetm beats audio screen, turns off and then restarts again through the whole process. it's jst looping now.
edit2: Flashed ViperXL, that's working. I guess HatkaXL just isn't for my phone.. sigh. I hope this thread helps anyone else.
devfrost said:
Thanks for the responses guys, you guys are saving me lots of stress and time.
You are correct that clean rom 5.1 flashes it for you, which is through its AROMA installer. However, HatkaXL also uses the AROMA installer, and there's a line in the installation screen where it says "flashing boot.img." - both ROMs have that line. Interestingly, it worked when I followed twistedddx's order so I'm going to try that again.
Yup, I have those in the same folder correctly. I always extract the boot.img from the rom zip into the folder with both fastboot and adb(how else would I able to have fastbooted in the first place?), always made sure the phone was in bootloader, plugged in, and in fastboot usb.
edit: I wiped, then installed hatkaXL, then fastboot flash boot boot.img, and now it starts, it gets past the red developmental screen, INTO the HTC Onetm beats audio screen, turns off and then restarts again through the whole process. it's jst looping now.
edit2: Flashed ViperXL, that's working. I guess HatkaXL just isn't for my phone.. sigh. I hope this thread helps anyone else.
Click to expand...
Click to collapse
Could be a kernel issue.. Try flashing stock kernel after flashing rom?... That's all I can think of. Also, I don't know if you do but I always wipe cache, dalvik, system, and then factory reset in twrp and I've never had any issues with any roms.
Sent from my One X using xda app-developers app
Q&A for [RECOVERY][bacon] TWRP 2.8.0.1 touch recovery [2014-09-12]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][bacon] TWRP 2.8.0.1 touch recovery [2014-09-12]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Recovery Partition Won't keep TWRP
I've tried to install TWRP 2.8.* and 2.7.* numerous times on my OPO. At first I was on 33R and everytime I would install TWRP, I could reboot into it once. After that the original CyanogenMod Simple Recovery would take over again. I went into Developer options and turned off "Update CM Recovery" then tried again. Same result, reboots one time into TWRP then everytime afterthat it goes into CMSR. The phone is rooted, and I did a fastboot oem unlock on the device so the bootloader should be unlocked as far as I can tell. I have since updated to 38R, re-rooted, and tried to reinstall TWRP and darned thing boots into twrp once then every other time goes into the stock recovery. Anyone have any ideas on how to make TWRP the permanent recovery??
Thanks,
fp
Nevermind!! Figured it out. Needed to do a fastboot format cache after flashing the twrp image to recovery.
I have a huge problem with TWRP I haven't been able to solve. Ever since I received my OPO a couple weeks ago I haven't been able to boot into TWRP. When booting into TWRP I always see artifacts and mostly a blue tint before the screen goes black. Only recovery I've successfully entered is Philz, but would prefer to use TWRP...
Flashing via fastboot always seem to be working without errors:
Code:
c:\Temp\android-adb_fastboot-16.01>fastboot flash recovery openrecovery-twrp-2.8.1.0-bacon.img
target reported max download size of 536870912 bytes
sending 'recovery' (12588 KB)...
OKAY [ 0.404s]
writing 'recovery'...
OKAY [ 0.234s]
finished. total time: 0.641s
Please watch these videos I took right after installing TWRP 2.8.1.0 to see what I'm dealing with:
youtu.be/jYJUfOOjaUE
youtu.be/GYcSjUKpOaE
I also posted about the issue in this thread, but would love to get some other opinions!
http://forum.xda-developers.com/showpost.php?p=56470225&postcount=13
And before you answer. I have unlocked bootloader and unticked "Update CM recovery" in dev settings. I have also tried almost all available versions of TWRP without success.
padalada said:
I have a huge problem with TWRP I haven't been able to solve. Ever since I received my OPO a couple weeks ago I haven't been able to boot into TWRP. When booting into TWRP I always see artifacts and mostly a blue tint before the screen goes black. Only recovery I've successfully entered is Philz, but would prefer to use TWRP...
Flashing via fastboot always seem to be working without errors:
Code:
c:\Temp\android-adb_fastboot-16.01>fastboot flash recovery openrecovery-twrp-2.8.1.0-bacon.img
target reported max download size of 536870912 bytes
sending 'recovery' (12588 KB)...
OKAY [ 0.404s]
writing 'recovery'...
OKAY [ 0.234s]
finished. total time: 0.641s
Please watch these videos I took right after installing TWRP 2.8.1.0 to see what I'm dealing with:
youtu.be/jYJUfOOjaUE
youtu.be/GYcSjUKpOaE
Click to expand...
Click to collapse
Have you tried flashing one of the TWRP zips using the
Philz recovery that works with your phone?
Edit: Hopefully these links to your videos are clickable so more people can see them.
http://m.youtube.com/watch?v=jYJUfOOjaUE&feature=youtu.be
http://m.youtube.com/watch?v=GYcSjUKpOaE&feature=youtu.be
meekrawb said:
Have you tried flashing one of the TWRP zips using the
Philz recovery that works with your phone?
Edit: Hopefully these links to your videos are clickable so more people can see them.
m.youtube.com/watch?v=jYJUfOOjaUE&feature=youtu.be
m.youtube.com/watch?v=GYcSjUKpOaE&feature=youtu.be
Click to expand...
Click to collapse
I've flashed TWRP using fastboot, Flashify and flashable zip in Philz - all without success. I've done "fastboot erase recovery" before flashing, but nothing seems to work. By the way, forgot to mention that I'm using latest stock rom, CM11s XNPH38R.
Thanks meekrawb! I'm not able to share clickable links because I need 10 posts on XDA first, I couldn't even post this reply with the links in your quote
Cant flash any zip file
I can't flash any zip file. Updated to the latest 2.8.1 also but no solution.
I am on CM11S 38R.
Any help would be appreciated. Screenshot attached.
Thanks
padalada said:
I've flashed TWRP using fastboot, Flashify and flashable zip in Philz - all without success. I've done "fastboot erase recovery" before flashing, but nothing seems to work. By the way, forgot to mention that I'm using latest stock rom, CM11s XNPH38R.
Thanks meekrawb! I'm not able to share clickable links because I need 10 posts on XDA first, I couldn't even post this reply with the links in your quote
Click to expand...
Click to collapse
I'd like to bump this issue as I'm having this exact issue on my own OnePlus One. I flash the latest 2.8.1.0 TWRP, reboot to it, it glitches out then slowly fades to blue then black. I wish I could understand it. At least I know this isn't an isolated incident with my One.
NotDisliked said:
I'd like to bump this issue as I'm having this exact issue on my own OnePlus One. I flash the latest 2.8.1.0 TWRP, reboot to it, it glitches out then slowly fades to blue then black. I wish I could understand it. At least I know this isn't an isolated incident with my One.
Click to expand...
Click to collapse
Since last post I have been troubleshooting for several hours. I've done a clean flash with 33R, 38R and 44S - with the same result. I started testing every recovery I could get hold of for bacon. Every CWM-based recovery worked without any problems. When it came to twrp following happened:
openrecovery-twrp-2.7.0.0-bacon.img - Frozen on bootup screen. Adb working though.
openrecovery-twrp-2.7.1.0-bacon.img - Frozen on bootup screen. Adb working though.
openrecovery-twrp-2.7.1.1-bacon.img - Frozen on bootup screen. Adb and vibration feedback working.
openrecovery-twrp-2.8.0.0-bacon.img - WORKING !!! But I'm not able to flash any zips.
openrecovery-twrp-2.8.0.1-bacon.img - Nothing works. Screen goes black.
openrecovery-twrp-2.8.1.0-bacon.img - Nothing works. Screen goes black.
It came as a supprise that 2.8.0.0 was actually booting! I sent a long mail to twrp team via 'general contact' on their home page, but with no response so far. I've also been in contact with katinatez that ports Temasec rom and unofficial twrp for our device. He has helped me troubleshoot some more. But I still don't know why twrp does not boot on my device.
padalada said:
Since last post I have been troubleshooting for several hours. I've done a clean flash with 33R, 38R and 44S - with the same result. I started testing every recovery I could get hold of for bacon. Every CWM-based recovery worked without any problems. When it came to twrp following happened:
openrecovery-twrp-2.7.0.0-bacon.img - Frozen on bootup screen. Adb working though.
openrecovery-twrp-2.7.1.0-bacon.img - Frozen on bootup screen. Adb working though.
openrecovery-twrp-2.7.1.1-bacon.img - Frozen on bootup screen. Adb and vibration feedback working.
openrecovery-twrp-2.8.0.0-bacon.img - WORKING !!! But I'm not able to flash any zips.
openrecovery-twrp-2.8.0.1-bacon.img - Nothing works. Screen goes black.
openrecovery-twrp-2.8.1.0-bacon.img - Nothing works. Screen goes black.
It came as a supprise that 2.8.0.0 was actually booting! I sent a long mail to twrp team via 'general contact' on their home page, but with no response so far. I've also been in contact with katinatez that ports Temasec rom and unofficial twrp for our device. He has helped me troubleshoot some more. But I still don't know why twrp does not boot on my device.
Click to expand...
Click to collapse
I am having the same exact symptoms as your OPO. With the 2.8.1.0 when I try to reboot to recovery either via adb command or the power menu or holding down the buttons from powered-off, I get the logo splash screen and then a weird and slow fade to black via a blue-ish tint. Very weird. I am going to try to flash 2.8.0.0 now and see what happens.
I tried flashing Unofficial TWRP 2.8.2.0 from katinatez just now. Everything seems to working for me now!!! First time booting it just rebooted after showing the splash-screen, but after next boot to recovery it seems to work. Tried flashing some various zips, all without any problem.
Grab it from here:
androidfilehost.com/?w=files&flid=19646
Noob here,
I have spent the last eight+ hours sifting thread by thread, video after video, and I haven't been able to get anywhere. I see an error similar (possibly the same) to the one I am experiencing now, so I hope I am in the right place.
I have used Wug's Bacon Root Toolkit to Unlock & Root my OnePlus One 64GB. I have copied over the CM11S file for the OPO from the Cyanogen website, as well as the gApps zip, to my SD. Now, when I go into TWRP, I choose Install> and I get a failed message.
My TWRP is 2.8.0.1, and I get a failed message. Now, I cannot boot my phone up (as I said, I am new to this) and I'm unsure of what steps I can take to get my phone to boot, whether back to ColorOS or CM11S.
Any help is appreciated.
hellatbs said:
Noob here,
I have spent the last eight+ hours sifting thread by thread, video after video, and I haven't been able to get anywhere. I see an error similar (possibly the same) to the one I am experiencing now, so I hope I am in the right place.
I have used Wug's Bacon Root Toolkit to Unlock & Root my OnePlus One 64GB. I have copied over the CM11S file for the OPO from the Cyanogen website, as well as the gApps zip, to my SD. Now, when I go into TWRP, I choose Install> and I get a failed message.
My TWRP is 2.8.0.1, and I get a failed message. Now, I cannot boot my phone up (as I said, I am new to this) and I'm unsure of what steps I can take to get my phone to boot, whether back to ColorOS or CM11S.
Any help is appreciated.
Click to expand...
Click to collapse
If the zip you downloaded says fastboot in the title you can only flash it with fastboot and not through twrp.
You can either download the cm11s zip again to your computer and flash it to your phone with fast boot, or you can download one of the cm nightlies and push it to your phone with adb and then flash that in twrp.
Either way, there is a lot more reading in your future.
If I were you I would start with @timmaaa guide over in general.
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Oneplus one sandstone black 64gb cm11s issues with latest twrp 2.8.0.4
Same problem touch not working and after a few seconds it will restart.
How to restore From OPO_Backup_EFS_2.0
Hi, i took back up of my Oneplus One using OPO_Backup_EFS_2.0.zip with TWRP , i just want to know how can i restore it back , is there any zip to restore or i have to use terminal commands, Thanks
when I use the app to install a new update of TWRP on my OPO i get a warning message to check if the partition is correct.
/dev/block/platform/msm_sdcc.1/by-name/recovery
Do i need to change this or can i click yes?
J0ch3nK said:
when I use the app to install a new update of TWRP on my OPO i get a warning message to check if the partition is correct.
/dev/block/platform/msm_sdcc.1/by-name/recovery
Do i need to change this or can i click yes?
Click to expand...
Click to collapse
You don't want to change it because that's the correct file path so yes.
Art Vanderlay said:
You don't want to change it because that's the correct file path so yes.
Click to expand...
Click to collapse
ty for the quick respond
so i clicked yes and also yes in next question to reboot in new recovey. but now it's stuck on boot logo for over a minute and TWRP doesn't seems to start. Did I missed anything else? I tried to update from 2.8.0.1 to 2.8.1.0 and also applied the SD patch the app displayed on launch.
Can I update to newest TWRP version when my ROM is on KitKat, or is newest TWRP only Lollipop?
edit.
never mind my latest question. I tried latest TWRP update and it works.
Falshing ROM using USB-OTG
I have done my homework and haven't found any suitable solutions yet
I just cannot connect USB-OTG.. TWRP 2.8.6.0
In the Mount screen.. I can check (Cross) Data.. Firmware.. All of it but NOT USB-OTG
Yes, I do have USB connected at the time of booting into Recovery!
Can some one please explain the procedure in detail as of how to flash via USB-OTG
#TIA
Help appreciated
So a while back I installed CM11, took some time but did it. Then I found out that CM12 is out. Installed that, no problems. But soon my phone started to get slow so I thought I'd go back to stock. Well.. Of course I forgot to do a backup when I installed CM11... So then I tried to install 11 again, maybe that could make my phone faster. Then the CM Recovery said that the CM11 can't be installed. After that I tried several other ROM's, but with no luck. I also had lost CWM when I installed CM12. So now I somehow managed to get TWPR but I can't do anything with it. When I wipe data and try to install a ROM, it fails. Right now I have some random 4.4.1 ROM installed but I don't have recovery and I can't install Cwm nor twpr without making the ROM disappear. So therefore I can't install any Google apps.
What I would eventually like to have is Cm11 with Google apps
Update
I unzipped FXP .zip file, in there made an IMG file from 'system' folder with ImgBurn, flashed boot.img and system.img with fastboot.
Rebooted phone.
CWM was on it and I flashed gapps.zip
Rebooted and everything working properly now.
Fastboot - recovery install fail
In SDK android tools I wrote
fastboot flash recovery [IMG name]
and it said
sending 'recovery' (size)
OKAY [0.0436s]
writing 'recovery'
FAILED (remote: command not allowed)
finished
So.. that happens with any recovery IMG I try to install.
The way I managed to finally install TWRP I wrote
fastboot flash boot recovery.img
Pretty sure that I shouldn't have done that but that installed TWRP so I could flash .zip files in it.
The only problem is that they all fail. I tried official CM11 nightly for taoshan, FXP CM11 for taoshan and neither of them worked.
The recovery said something about M5 file.. that it skipped checking it or something. Since I dont know what that means, I dont know what I'm doing wrong. I'm also pretty sure that the FXP CM11 is the excact same one I used the first time around and then it worked.
So.... any ideas about my problem?
I'm new to the forums, so if I don't explain some correctly let me know. I have a Envizen V100 mdt running 4.4 and it crashed. I downloaded all the tools and new image for the company that that makes the tablet.
I have flashed it successfully once, but it crashed again. Now when I use thier flash tool it won't reconize the tablet. I cen boot to fastboot only, when I try to boot into recovery, it just keeps rebooting and
hangs up at the logo. I tried flashing using fastboot, first by flashall, then flashing each seperate img and it still won't boot past the logo. Has anyone experienced this problem with this tablet? By the way,
I have downloaded the image and tools several times and still can't get it to reflash properly or even get to adb.
free14 said:
I'm new to the forums, so if I don't explain some correctly let me know. I have a Envizen V100 mdt running 4.4 and it crashed. I downloaded all the tools and new image for the company that that makes the tablet.
I have flashed it successfully once, but it crashed again. Now when I use thier flash tool it won't reconize the tablet. I cen boot to fastboot only, when I try to boot into recovery, it just keeps rebooting and
hangs up at the logo. I tried flashing using fastboot, first by flashall, then flashing each seperate img and it still won't boot past the logo. Has anyone experienced this problem with this tablet? By the way,
I have downloaded the image and tools several times and still can't get it to reflash properly or even get to adb.
Click to expand...
Click to collapse
if you havent tried wiping the data yet, and dont have anything important you are trying to save, i would try that.
fastboot -w
thats all i could suggest, sorry.
bweN diorD said:
if you havent tried wiping the data yet, and dont have anything important you are trying to save, i would try that.
fastboot -w
thats all i could suggest, sorry.
Click to expand...
Click to collapse
I have tried wiping everything and usually it works, but it still won't boot. I have been trying to boot different images, but ist always hangs up on:
"C:\ADB>fastboot boot boot_310.img
creating boot image...
creating boot image - 6465536 bytes
downloading 'boot.img'...
OKAY [ 0.339s]
booting...
That is where I am a now. Thanks for your help.
free14 said:
I have tried wiping everything and usually it works, but it still won't boot. I have been trying to boot different images, but ist always hangs up on:
"C:\ADB>fastboot boot boot_310.img
creating boot image...
creating boot image - 6465536 bytes
downloading 'boot.img'...
OKAY [ 0.339s]
booting...
That is where I am a now. Thanks for your help.
Click to expand...
Click to collapse
one other thing came to mind as i read your reply.
i have 0 experience with your device, but on some devices you can not downgrade software. sometimes just certain partitions, sometimes all of them. a bootloop is a common side effect of trying.
i would try the most current software thats ever been on the device, and flash the partition table first, if one is included.
thats all i got for now
Hey,
so, I'm really sorry if this has been asked before, but I've searched far and wide for something I can do and I have run out of ideas.
I tried a custom rom on my Oneplus 6 today and wanted to revert back to my old rom, which led to everything spiraling downwards. First I tried restoring my TWRP backup but that oddly sent me into a bootloop. Afterwards I tried installing the zip for the stock rom of OB5, which I was on before and just recovering the data partition, which worked and I could boot, but oddly enough the stock Oneplus launcher was gone. Since I couldn't open any apps without the launcher, I couldn't just install it via an apk or something, so I tried installing the stock rom and afterwards just recovering the data, boot and system partitions, which sent me into a bootloop which keeps booting into fastboot. But now, I am not able to boot the twrp.img anymore with the error shown in the title:
Code:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
So then I downloaded the stock kernel boot img in the hopes that booting it would work, which it didn't. I tried flashing it to the boot_a and boot_b partitions: same result. So now I'm out of ideas. Can anyone help me with figuring out what I can do to recover my oneplus 6 from the bootloop without erasing the internal storage (data partition is not that important, but it would really suck to lose my internal storage). Thanks
EDIT: After finding this fastboot flashable rom and using the flash-all-partitions-fastboot.bat, I could at least boot into recovery without it bootlooping again. I then used this opportunity to back up all my important files to a USB stick and clean flashed OOS, so now I finally resolved it
ddominikt said:
Hey,
so, I'm really sorry if this has been asked before, but I've searched far and wide for something I can do and I have run out of ideas.
I tried a custom rom on my Oneplus 6 today and wanted to revert back to my old rom, which led to everything spiraling downwards. First I tried restoring my TWRP backup but that oddly sent me into a bootloop. Afterwards I tried installing the zip for the stock rom of OB5, which I was on before and just recovering the data partition, which worked and I could boot, but oddly enough the stock Oneplus launcher was gone. Since I couldn't open any apps without the launcher, I couldn't just install it via an apk or something, so I tried installing the stock rom and afterwards just recovering the data, boot and system partitions, which sent me into a bootloop which keeps booting into fastboot. But now, I am not able to boot the twrp.img anymore with the error shown in the title:
Code:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
So then I downloaded the stock kernel boot img in the hopes that booting it would work, which it didn't. I tried flashing it to the boot_a and boot_b partitions: same result. So now I'm out of ideas. Can anyone help me with figuring out what I can do to recover my oneplus 6 from the bootloop without erasing the internal storage (data partition is not that important, but it would really suck to lose my internal storage). Thanks
Click to expand...
Click to collapse
at this point, https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 is your only option that will get you up and running again. this WILL wipe the whole device including internal storage. Or you could try the fastboot rom thread, https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665.
MrSteelX said:
at this point, https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 is your only option that will get you up and running again. this WILL wipe the whole device including internal storage. Or you could try the fastboot rom thread, https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665.
Click to expand...
Click to collapse
Yeah I guess I'll try the fastboot rom now without wiping the internal storage. If that at least helps me to boot into recovery, I can at least back up my most important files. If not, there is no other option I guess. Unless anybody has any ideas left for me
ddominikt said:
Yeah I guess I'll try the fastboot rom now without wiping the internal storage. If that at least helps me to boot into recovery, I can at least back up my most important files. If not, there is no other option I guess. Unless anybody has any ideas left for me
Click to expand...
Click to collapse
Asaik fastboot flash all will erase your internal drive but just don't take my work read on the thread, I have been through this and have lost data so now I try my best to keep my data stored elsewhere like online storage etc, cheers