Hi a month ago i flashed twrp 2.8.7 on my M8 to make backups and use helium for app backup (with supersu). today an OTA update came out, so i flashed back the stock recovery and started the OTA update. it went through but it hang at the white HTC One startscreen. after 15 mins i shut it down and rebooted it.
it showed the white screen with the small htc logo and then immediately wents black.
the power button does not respond so i did a "soft reset" (powerbutton and vol+) but that just brings it back in the unusable state.
what can i do now?
can be closed, after the battery drained i was able to restore it. (damn phones without removable batteries)
I'm having the same problem, I received a message last night that an update was downloaded to my phone. Sometime in the middle of the night my phone restarted and it's now frozen at the htc one splash screen.
My bootloader is unlocked and the phone was rooted, but have stock recovery. Also, my phone was encrypted.
I was able to get into Fastboot by holding vol-up+pwr, then when the screen goes blank immediately switch from vol-up to vol-down. I tried factory reset from Fastboot menu and also from the Recovery menu, but problem remains. I also loaded TWRP through Fastboot and tried Data Wipe, but still doesn't work.
Any suggestions?
dwestall said:
I'm having the same problem, I received a message last night that an update was downloaded to my phone. Sometime in the middle of the night my phone restarted and it's now frozen at the htc one splash screen.
My bootloader is unlocked and the phone was rooted, but have stock recovery. Also, my phone was encrypted.
I was able to get into Fastboot by holding vol-up+pwr, then when the screen goes blank immediately switch from vol-up to vol-down. I tried factory reset from Fastboot menu and also from the Recovery menu, but problem remains. I also loaded TWRP through Fastboot and tried Data Wipe, but still doesn't work.
Any suggestions?
Click to expand...
Click to collapse
I'm in the same boat. My rooted, s-off but otherwise OEM phone updated itself and now hangs at boot. (I haven't tried anything yet that would wipe my data.) Other weird issue I've seen (posted elsewhere) is that my external card won't keep writes made within TWRP (backup show up one minute in TWRP's file manager, then the new ones disappears a few minutes later).
I was able to restore an old nandroid backup I made and stored on my PC, so now I'm at least back up and running though with an order version of Android (4.4.4). When I checked for updates it says I have the latest. Hopefully, it will eventually update.
I wonder if my device encryption caused problems with the update. Does anyone else use device encryption? Did you have problems with the update?
generalprobe said:
Hi a month ago i flashed twrp 2.8.7 on my M8 to make backups and use helium for app backup (with supersu). today an OTA update came out, so i flashed back the stock recovery and started the OTA update. it went through but it hang at the white HTC One startscreen. after 15 mins i shut it down and rebooted it.
Click to expand...
Click to collapse
Where did you find the stock recovery? Thanks.
sorry i did not see your post @indiana99
first do the following please: fastboot getvar version-main
and then proceed to the site here: http://www.handy-faq.de/forum/htc-one-m8-firmwaresammlung-ruus-otas-backups-t301918/#comment-2710920 and find a matching version.
when you found one, for me it was 4.16.401.10 but i have an unbranded m8 you proceed with these commands:
fastboot flash recovery name_of_the_recovery.img
and then afterwards
fastboot erase cache
Thanks.
generalprobe said:
sorry i did not see your post @indiana99
first do the following please: fastboot getvar version-main
and then proceed to the site here: http://www.handy-faq.de/forum/htc-one-m8-firmwaresammlung-ruus-otas-backups-t301918/#comment-2710920 and find a matching version.
when you found one, for me it was 4.16.401.10 but i have an unbranded m8 you proceed with these commands:
fastboot flash recovery name_of_the_recovery.img
and then afterwards
fastboot erase cache
Click to expand...
Click to collapse
Thanks.
generalprobe said:
first do the following please: fastboot getvar version-main
and then proceed to the site here: http://www.handy-faq.de/forum/htc-one-m8-firmwaresammlung-ruus-otas-backups-t301918/#comment-2710920 and find a matching version.
Click to expand...
Click to collapse
He won't find the matching version on that page. AT&T is 502, which is not listed.
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
generalprobe said:
when you found one, for me it was 4.16.401.10 but i have an unbranded m8
Click to expand...
Click to collapse
Then you're posting to the wrong forum section, this one is specifically for the AT&T version.
Related
Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.
I have been playing around with this for the past 24 hours almost non-stop. The device information:
M7 T-Mobile (converted to GE 4.3)
No OS installed at this point
HBOOT 1.54
S-ON (Unfortunately big mistake not to take care of this during conversion)
Unlocked Bootloader
Can do adb and fastboot commands, but anything that I try to write to system (from a ZIP file either RUU or custom ROM, they error out)
fastboot oem rebootRUU then trying to flash would give me: FAILED (remote: 99 unknown fail)
trying to update the bootloader from the same package I get: FAILED (remote: 12 signature verify fail)
I can flash boot and recovery images and that's about it, tried both CWM and TWRP to install CynogenMod, they both fail.
Here is the history of what happened:
Day one, I wanted to convert to GE so I did and everything worked, the device wasn't rooted or anything so it was fully GE. (S-ON though). Yesterday, when 4.4 OTA came, I went aehead and installed, everything installed fine OS booted to lock screen, but as soon as launcher was initiated, the phone would restart within 3 seconds (first mistake was to update through OTA, but I thought I was converted completely so trusted it). Second mistake was I said, well I will just reinstall all the apps since nothing worked after trying for hours so I did a wipe and reset factory and now, it would boot to the setup screen and after 3 seconds like before, it would restart, so I decided to get rid of whatever on there from fastboot and that's where I stand today. I played with it for hours yesterday and today and I have tried the toolkit, revnov (which doesn't work with 1.54 and rumrunner requires the device to boot to OS, which I don't have).
I feel like I have managed to brick it even with being able to send and execute commands.
Any help would be immensely appreciated.
EDIT 1:
TWRP comes up with a password prompt right at the beginning as if the data on the phone is encrypted. I never encrypted the phone in any way, I did have corporate email that had the right to wipe the device.
Try sideloading a Rom from recovery from your pc to phone
Sent from my HTC One using xda app-developers app
---------- Post added at 07:14 AM ---------- Previous post was at 07:12 AM ----------
I know one thing never hit reboot if you ever see No Os installed while In recovery
That means the bootloaderr will be wiped
...I did this with my s3 had to jtag repair.
Best of luck
Sent from my HTC One using xda app-developers app
Sideload won't work, it immediately fails on TWRP (last log is updating partitions), in fact, when on CWM, adb wouldn't load the device at all (no devices listed), but when TWRP, it works just fine.
lojak29 said:
Try sideloading a Rom from recovery from your pc to phone
Sent from my HTC One using xda app-developers app
---------- Post added at 07:14 AM ---------- Previous post was at 07:12 AM ----------
I know one thing never hit reboot if you ever see No Os installed while In recovery
That means the bootloaderr will be wiped
...I did this with my s3 had to jtag repair.
Best of luck
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Try uninstalling and re-installing your drivers on your PC and try again.
I actually got it back. I gave myself a clue on here, apparently, the phone when factory resetting encrypted the device and I went through fast because the device would restart if I didn't so couldn't read all pop-ups. I went ahead and encrypted which is why TWRP and CWRM didn't work, tried many methods to remove the encryption and just wipe everything off. Nothing worked, the data couldn't even mount to be wiped therefore no ROM would successfully install. So I reinstalled recovery of GE build that I used for factory reset, went into that recovery and wiped cach and data completely and this time it worked (no other version worked before). After that it was easy to TWRP or any other custom recovery to get the stock ROM on the phone and now it's all back. Now I am back to completely stock with tampered flag and unlocek bootloader. Eventually, I will do a proper conversion to GE because I am starting to dislike the SENSE (which I knew I would) because of all the stuff I don't use and worse battery management and mobile data unnecessarily updating things I don't use. This was such a experience, as much as I wanted to keep the Nexus 5, had to return it.
Thanks all for the suggestions.
Is there any way I can get rid of tempered flag, I know I ran across something well hidden, ant link would be helpful, thanks.
what is meant with "GE build"? I am stuck in the same situation you have been, but have no clue what you did to get it back to life. THanks for a hint.
I meant version by build. You can find an RUU for the version you were on (4.2.2 or 4.3 or 4.4) and take out the recovery.img and in fastboot, flash recovery with that image and go in recovery and wipe data. I hope this helps.
MrWhat said:
what is meant with "GE build"? I am stuck in the same situation you have been, but have no clue what you did to get it back to life. THanks for a hint.
Click to expand...
Click to collapse
Hi,
I'm a bit new here and running a good old-fashioned stock Inc 4G LTE, never rooted or flashed to new ROM. It DOES have the latest OTA update from Verizon a couple months ago.
This morning my phone suddenly went off after working OK. Then when trying to restart, I get an infinite boot loop and it won't get past the red Droid screen. I've searched various threads and tried what I think are the most obvious things, and nothing seems to help. But I want to make sure there are no other options before I throw it in the trash.
Here's what I tried:
- Tried entering Safe Mode by holding down volume key after HTC screen comes on. Makes no difference, does not enter Safe Mode.
- Get to HBOOT OK. Says 'LOCKED' and I am running HBOOT v.1.15.0000.
- - In HBOOT, I've tried running Recovery a couple times. Seems to go OK, but just starts looping when restarting.
- - In HBOOT, tried running Recovery > Wipe Cache Partition. Says cache is cleared.
- - In HBOOT, tried running Recovery > Wipe data/factory reset. Seem to go through OK.
- - In HBOOT, tried running Factory Reset.
- - In HBOOT, tried running Clear Storage.
- Pulled battery and tried spare.
- Removed SD card.
Some history - this phone has always been very sluggish. A few months ago started shutting down when doing camera intensive things (would jump to battery at critical level). So I did a factory reset a couple weeks ago and was slowly adding some of the essential apps back in. It crashed trying to upload photos to Facebook. Last night I had just moved some apps to the Phone storage and set my Sound Profile app to change profiles in the morning. This is about the time the phone crashed.
Anything else I should try before giving up?
Can I try to root and install a custom ROM to fix when in this state? Is this now possible with latest OTA update?
If custom ROM is last chance, is there a really solid one running 4.3 and Sense?
THANKS! May be time to get a HTC One or iPhoney, as I'm just not into huge phones that are coming out...
iRunNaked said:
If your on bootloader 1.15.0000 and now 1.16.0000, try using the stock Ruu and restoring the phone. If not, try rebooting in bootloader and factory reset.
If that doesn't work, gain root (if you haven't) and get s-off/unlock bootloader/CID set to 111111, and try a custom rom. If all else fails, take it back to stock and unroot/s-on/CID back to VZW/Relocked.
Call Verizon and tell them you need a replacement. The phone randomly gets real hot and reboots. They should send you a new one no problem.
I girlfriend had the random reboots, ending up getting it replaced. Now shes on her 4th or 5th incredible lte. (data Issues & random reboots)
Click to expand...
Click to collapse
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
jethrodesign said:
I tried running a stock 2.17.. RUU, but got a "Failed" message because the software was too old. I'm guessing that is because I'm on the newer 2.19.. OTA update?!? Anyone know where to get a RUU file for the latest 2.19 version? I've been searching with no luck.
I'll have to research how to root/unlock the phone when it won't boot. Any specific threads that have fairly detailed instructions would be appreciated.
Thanks!
Click to expand...
Click to collapse
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
jethrodesign said:
I looked at the thread about how to successfully root & flash the phone when it has the Verizon OTA update (2.19.xx) found here: http://forum.xda-developers.com/showthread.php?t=2664460.
But it appears at first glance that to do it the phone needs to be booted up and connected to the computer via USB. I can only get my phone to the HBOOT screen, nothing else.
- Can anyone confirm that to unlock and/or flash a new ROM on this phone that it has to be able to boot up? No way to do it on my phone with the 2.19 software and constant rebooting?
Thanks. It's cosmetically perfect, so I feel bad about throwing it away. If I can get it back up somehow I could at least sell it or give it to someone in need.
Click to expand...
Click to collapse
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
stringedonbass said:
If you want to use mdmower's "temp-root" trick, then you'll need to be able to access the device through Android Debug Bridge. Can you see the device if you type
Code:
adb devices
after booting up past the bootloader?
Click to expand...
Click to collapse
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
jethrodesign said:
Hi. I've never tried running ADB. Not very familiar with it at all. But my phone will not boot past the HBOOT option. No matter what I've tried, it will just go into a rebooting loop. I'm assuming it needs to be fully booted up to work with ADB?!?
- Is there an RUU for the latest software update (2.19.xx) somewhere that I can try running to see if it will help it fully boot?
- Any other options?
Thanks!
Click to expand...
Click to collapse
Yes, my understanding is that to use adb, you need to be able to boot into the OS with usb debugging turned on. Hopefully someone will come along with a worthwhile response!
Is anyone aware of more current RUU's than are menteioned here?
http://forum.xda-developers.com/showthread.php?t=1770978
---------- Post added at 05:19 PM ---------- Previous post was at 05:07 PM ----------
If the phone failed as a completely stocked phone, why not try returning as opposed to figuring out how to root a broken phone?
Hi everyone, so this is my first post here on Xda, heard a lot of good things though
Anyways, I just re-rooted my HTC One M8 at&t model for the second time, I have rooted before, but had some issues so I decided to unroot and relock it, that is until today, when android 5 came out for the developer edition I decided I would try to convert mine so I could install the official ota.
So I unlocked my bootloader and flashed
./fastboot flash recovery openrecovery-twrp-2.8.4.0-m8.IMG
Said it wrote it successfully, so I tried to boot into recovery to flash super su.
When I tried however, it just sat and hung at the "entering recovery" screen.
I held down the power and volume up to get back to my home screen and retried after booting back into the bootloader.
Same thing. Not sure what I did wrong. I installed TWRP for gsm models (like I should have, right?).
Is it possible that somehow the old version of TWRP from my previous rooting experience is creating conflict with the one I just flashed? I'm really new to all this, so thanks for putting up with my uneducated self
Any ideas?
Thanks in advance!-Z
PR4X15 said:
Same thing. Not sure what I did wrong. I installed TWRP for gsm models (like I should have, right?).
Click to expand...
Click to collapse
Right, as long as its not meant for CDMA or the dual SIM version, you are good to go.
Failure to boot into recovery from bootloader can usually be solved by fastboot erase cache, and install TWRP again. Probably just a problem with TWRP not being properly installed the first time around.
Or even try an older version. TWRP 2.8.4.0 is really new, so maybe there are issues.
So after updating my bootloader to the new version so I can run Android Nougat however I wasn't getting any LTE connection and decided to restore the EFS backup I had from android MM.
My phone started having problem more problems (SIM card not being detected) and I decided to run the OPX recovery and switch back to default.
However this resulted in my bootloader getting locked for some reason and whenever I try to reboot my phone the screen is black and the LED indicator turns white.
I can boot into the factory OPX recovery but I'm forced to use the volume and lock buttons because I can't use my touchscreen whilst using this (no idea whether this is normal).
I can still boot into fastboot mode and have tried to sideload a new ROM however this has been to no avail.
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Hmm, okay thanks for your reply. But is it really a hardware problem? It sounds weird but maybe replacement is a way...
It strange, since I had the problem with my phone there are 3-4 new threads now in this forum were people have exactly this problem, black screen with white led.
I will not flash my phone again in the foreseeable future and just use gravitybox instead.
Mutchatcho said:
Hey, I got that exact same problem. All was fine, did a backup and wiped as every time to try out a new rom. It boot normaly and was tweaking the rom. Then I decided to restore my backup, wiped as every time and restored my backup. Till then my SIM card is not being detected and some strange things happend like I couldn't enter the recovery with advanced reboot. After that I followed the unbrick guide and my bootloader is also locked but could not boot into the rom. After bootscreen the screen is black and the LED turns white. I can also boot into the factory OPX recovery.
What happened here? Anyone some ideas?
Click to expand...
Click to collapse
I did the exact same thing as you and ended up in this situation.
adefigo said:
I had the same problem, I had to trick oneplus-support to do it on warranty, see http://forum.xda-developers.com/showpost.php?p=70182036&postcount=16 and http://forum.xda-developers.com/showpost.php?p=70184136&postcount=18
Today I got my phone back with a new mainboard.
Click to expand...
Click to collapse
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Miniheadshot said:
How did you unlock the bootloader or even install KingRoot? The problem is that my bootloader is locked, that I have no way to unlock it, no proper recovery and that I can't boot into my ROM.
Also does anyone know whether Simplesurance would cover my phone? Since it does state it covers "incorrect use" (or something along those lines).
Click to expand...
Click to collapse
With the new mainboard and the new rom build, it is impossible to use twrp or root. I didn't know that when I wrote I would be using gravitybox from now on and not flash custom roms again.
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Mutchatcho said:
Just a quick update. Got my phone back and they also replaced the mainboard. It's now on the latest OOS but I can do everything as before. So hopefully it will survive longer as before - what ever it was...
Click to expand...
Click to collapse
What is your built number?
adefigo said:
What is your built number?
Click to expand...
Click to collapse
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Mutchatcho said:
You mean build number of OOS? Honestly don't know cause I directly flashed AOSPExtended + Arsenic. :silly: but was the v3.1.4.
Click to expand...
Click to collapse
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Ah okay, I didn't know that. Obviously then I got maybe the other one.. but not sure if this makes the difference.
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
dchrono said:
What you guys are describing as a common flash of new ROM and wipe to restore backup sounds like something's left out. Did you change twrp versions between flashing and restoring? Was your backup with 3.0.2 twrp and new flash with 3.0.3?
Cause these issues usually occur when recovery versions change
Click to expand...
Click to collapse
No, did not change twrp versions during flashing new ROM and wipe to restore backup. Don't know if I remember correctly but I think I was on Bluesparks twrp (was it 3.0.0?) and did not change that during the processes.
i also had same problem
i try to update my twrp recovery with flashify. it was successful but now i cant boot into recovery. i dnt know bootloader is locked or not. i can use many fastboot commands like fastboot reboot-bootloader, fastboot continue. please help me. i try many times to update or remove twrp but nothing happend. rom is working.
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
I never changed twrp version during this until it was removed by MsmDownloadTool.
I also noticed that adb sideloading using OOS's old stock recovery with a OOS OTA zip doesnt work, it either gets stuck at logo or loops. Sideloading newer OTA zips kills the phone more because I tried to flash a MM zip and found that recovery no longer works. I've tried redownloading the MsmDownloadTool package and using this other modified MsmDownloadTool here a few replies down https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Another thing I noticed is that windows detects a bunch of unreadable local drives, with one readable containing only an 'images' folder, with useful-looking stuff like adsp.b00, adsp.b01 all the way to adsp.b12 and also .mbt files. I can provide the full list if it's useful. It's also detected in the device manager as "Marshall London HS-USB Diagnostics 9006 (COM6)" under Ports.
I really hope that I don't need to send this phone back to oneplus.
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt work, so I tried re-restoring EFS, wiping, formatting and wipe+flashing various ROMs all with a still unrecognised sim. Finally I decided I had enough a used the MsmDownloadTool, but it softbricked my phone with the blank screen and white LED if I try to boot into system.
Click to expand...
Click to collapse
Exactly what I did and what happened to my phone. I had to send it back to repair and got it back with a new mainboard in a state that I cannot use twrp any more.
adefigo said:
There are two v3.1.4 builds, ONE E1003_14_161107 and E1003_15_161107. My new Mainboard came with the latter and now twrp doesn't find any partition. So no root or custom rom for me any more.
Click to expand...
Click to collapse
Did you try to adb sideload flash the 3.1.4 on the 14 version?
Clae said:
Damn, same problem here. I tired to flash a new ROM (the android base for SailfishOS 2) and it failed, was getting late so I decided to restore the backup I just made (the backup had everything selectable in twrp including EFS backed up). After rebooting the sim, sd card and wifi didnt phone back to oneplus.
Click to expand...
Click to collapse
I had flashed a ROM and wanted to restore a backup of MOOS. The back up restored no problem but when I booted it wouldn't detect sim trays and no wifi. When I typed *#06# no iemi's and finally when I checked about phone I had no baseband. I had a back up of efs and persist but wouldnt help. If this sounds like your issue or if anyone's having this problem its actually easy fix. With adb commands had to delete modem1 and modem2 files. I had my doubts but after reboot sims trays detected, wifi and iemi's restored.